On Sat, Jan 16, 2010 at 1:40 PM, Drew Farris <drew.far...@gmail.com> wrote:
> Mahout does per-test forking, which means we're forking off a new JVM > for each unit text execution, this adds overhead to tests that takes > 0.2s to complete. Is per-test forking strictly needed? > It shouldn't be. I would count it a bug if it were. > ... wall time 30s (!) or so. ... attempting to reading from /dev/random. > > 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. -- Ted Dunning, CTO DeepDyve
