jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@adobe.com>
Subject Re: slow observation tests
Date Wed, 23 Oct 2013 07:29:09 GMT

IMHO we should consider lowering the interval for the default
setup. if i remember correctly we added sleeps to some of
our internal integration tests because they used to fail due
to that fact.

i recently discussed this with christian keller and he argued
that this is likely to cause troubles in productive systems.
IMO he is right and we should try to prevent this kind of issues
by having a suitable default setup.

kind regards

On 10/23/13 9:10 AM, "Marcel Reutegger" <mreutegg@adobe.com> wrote:

>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.
> Marcel

View raw message