[ https://issues.apache.org/jira/browse/MATH1154?page=com.atlassian.jira.plugin.system.issuetabpanels:commenttabpanel&focusedCommentId=14161873#comment14161873
]
Thomas Neidhart commented on MATH1154:

I like the solution myself, thats why I am doing what I have outlined before:
* use a null rng in places where I know that no sampling will be used (and which is hidden
to users anyway), namley in the inference tests
* reopen MATH1124 to discuss the addition of lazy rng initialization in the distribution
classes so that other users can also benefit from it (and may not be as advanced to know details
about the use of a rng and when one can provide a null instance)
> Statistical tests in stat.inference package are very slow due to implicit RandomGenerator
initialization
> 
>
> Key: MATH1154
> URL: https://issues.apache.org/jira/browse/MATH1154
> Project: Commons Math
> Issue Type: Bug
> Affects Versions: 3.3
> Reporter: Otmar Ertl
> Attachments: MATH1154.patch, math3.patch
>
>
> Some statistical tests defined in the stat.inference package (e.g. BinomialTest or ChiSquareTest)
are unnecessarily very slow (up to a factor 20 slower than necessary). The reason is the implicit
slow initialization of a default (Well19937c) random generator instance each time a test is
performed. The affected tests create some distribution instance in order to use some methods
defined therein. However, they do not use any method for random generation. Nevertheless a
random number generator instance is automatically created when creating a distribution instance,
which is the reason for the serious slowdown. The problem is related to MATH1124.
> There are following solutions:
> 1) Fix the affected statistical tests by passing a lightweight RandomGenerator implementation
(or even null) to the constructor of the distribution.
> 2) Or use for all distributions a RandomGenerator implementation that uses lazy initialization
to generate the Well19937c instance as late as possible. This would also solve MATH1124.
> I will attach a patch proposal together with a performance test, that will demonstrate
the speed up after a fix.

This message was sent by Atlassian JIRA
(v6.3.4#6332)
