lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lance Norskog <goks...@gmail.com>
Subject Re: TestCodecs running time
Date Fri, 09 Apr 2010 20:20:00 GMT
I have found it useful to keep two lists of tests: the slow tests and
the fast tests. Maybe the TestSuite feature would work for this
purpose?

An @SlowTest annotation would be even better. JUnit might have a tool
to do this filtering.

On Fri, Apr 9, 2010 at 2:49 AM, Michael McCandless
<lucene@mikemccandless.com> wrote:
> It's also slow because it repeats all the tests for each of the core
> codecs (standard, sep, pulsing, intblock).
>
> I think it's fine to reduce the number of iterations -- just make sure
> there's no seed to newRandom() so the distributing testing is
> "effective".
>
> Mike
>
> On Fri, Apr 9, 2010 at 12:43 AM, Shai Erera <serera@gmail.com> wrote:
>> Hi
>>
>> I've noticed that TestCodecs takes an insanely long time to run on my
>> machine - between 35-40 seconds. Is that expected?
>> The reason why it runs so long, seems to be that its threads make (each)
>> 4000 iterations ... is that really required to ensure correctness?
>>
>> Shai
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>



-- 
Lance Norskog
goksron@gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message