Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of mreutegg@adobe.com designates
 64.18.1.236 as permitted sender)
From: Marcel Reutegger <mreutegg@adobe.com>
To: "oak-dev@jackrabbit.apache.org" <oak-dev@jackrabbit.apache.org>
Date: Wed, 23 Oct 2013 08:10:02 +0100
Subject: slow observation tests
Thread-Topic: slow observation tests
Thread-Index: Ac7PvS1G7kxLoimKRL6I5wlFkpH4/g==
Message-ID: 
 <9C0FC4C8E9C29945B01766FC7F9D389818A7A2C624@eurmbx01.eur.adobe.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi,

our JCR observation tests are quite slow compared to Jackrabbit.
In an offline discussion with Michael, we suspected the way tests
are written is the culprit. at least the TCK tests may wait up to
five seconds for events. we thought some excluded tests slow
down execution because those do not get expected events and
therefore wait five seconds.

after a closer look I don't think that's the case. even tests, which
succeed are kind of slow. I rather think it's the polling interval
in oak. AFAIU oak polls for changes every second. this also means
events are delivered with an average delay of half a second.

would it be possible to lower the interval, at least for the tests?
I think this would speed up those tests significantly.=20

Regards
 Marcel