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 <ser...@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-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to