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 On Sun, Jan 17, 2010 at 5:47 AM, deneche abdelhakim <adene...@gmail.com> wrote: > I'm getting similar slowdowns with my VirtualBox Ubuntu 9.04 > > I'm suspecting that the problem is not -only- caused by RandomUtils because: > > 1. I'm familiar with MerseneTwisterRNG slowdowns (I use it a lot) but > the test time used to be reported accurately by maven. Now maven > reports that a test took less than a second but it actually took a lot > more ! > > 2. Most of my tests actually call RandomUtils.useTestSeed() in setup() > (InMemInputSplitTest included) but the tests still take a lot of time, > and again its not reported accurately by maven > > 3. I generally launch a 'mvn clean install' every Thursday. I never > got this slowdowns until last Thursday (dit we change anything that > could have caused this slowdowns) > > On Sun, Jan 17, 2010 at 12:33 AM, Benson Margulies > <bimargul...@gmail.com> wrote: >>>> >>> Unit tests should generally be using a fixed seed and not need to load a >>> secure seed from dev/random. I would say that RandomUtils is probably the >>> problem here. The secure seed should be loaded lazily only if the test seed >>> is not in use. >> >> The problem, as I see it, is that the uncommons-math package start >> initializing a random seed as soon as you touch it, whether you need >> it or not. RandomUtils can only avoid this by avoiding uncommons-math >> in unit test mode. >> >>> >>> >>> >>> -- >>> Ted Dunning, CTO >>> DeepDyve >>> >> >
