Not sure what's going on or why that revision would have anything to
do with the slowdown... the only thing of substance it did was
actually let the SamplingIterator test run but it doesn't take long.

I agree with not forking a JVM per test, so will make that change.

Also, yes, we need tests to be deterministic. This is the theory
behind why all code should obtain a Random from RandomUtils, and, all
tests should configure RandomUtils to use a fixed seed in setUp().
This isn't 100% true. Mind if I indeed finally fix this?

I don't know of any further issues with MersenneTwisterRNG though --
what's the issue? Don't care what it does with /dev/random as long as
in test mode we are seeding it with the same seed, and that's what
RandomUtils does.


On Sun, Jan 17, 2010 at 7:29 AM, deneche abdelhakim <adene...@gmail.com> wrote:
> removing the maven repository does not solve the problem, neither a
> fresh checkout of the trunk.
>
> but older revisions don't show any slowdown!!! I tried the following 
> revisions:
>
> Those old revisions seem Ok:
> ------------------------------------------------------------------------
> r896946 | srowen | 2010-01-07 19:02:41 +0100 (Thu, 07 Jan 2010) | 1 line
> MAHOUT-238
> ------------------------------------------------------------------------
> r897134 | robinanil | 2010-01-08 09:23:22 +0100 (Fri, 08 Jan 2010) | 1 line
> MAHOUT-221 Missed out two files while checking in FP-Bonsai
> ------------------------------------------------------------------------
> r897405 | adeneche | 2010-01-09 11:02:49 +0100 (Sat, 09 Jan 2010) | 1 line
> MAHOUT-216
>
>
>>>> The slowdowns start at this revision !!!
> ------------------------------------------------------------------------
> r897440 | srowen | 2010-01-09 13:53:25 +0100 (Sat, 09 Jan 2010) | 1 line
> Code style adjustments; enabled/fixed TestSamplingIterator
>

Reply via email to