It doesn't affect the random numbers being generated. But it does eat bits of entropy from /dev/random. That can then get starved and block until more entropy is derived. Since the reading is done in a static block instead of on construction, the cost can't be avoided.
On Sun, Jan 17, 2010 at 4:31 AM, Sean Owen <sro...@gmail.com> wrote: > But does that affect code which instantiates a MersenneTwisterRNG with > its own seed? > > On Sun, Jan 17, 2010 at 12:24 PM, Benson Margulies > <bimargul...@gmail.com> wrote: > >> 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 > >> > > > > Olivier and I found the Mersenne code touching the > > SecureRandomNumberGenerator, which goes and talks to /dev/random, all > > in static blocks before any seeds are used. > -- Ted Dunning, CTO DeepDyve
