3 ms·
The author does address the perf & efficiency concerns, though I have no opinion on the strength of their conclusions. But I think this is like everything else
by kelnos 3y ago
The author does address the perf & efficiency concerns, though I have no opinion on the strength of their conclusions.
But I think this is like everything else: don't prematurely optimize. If you start with a CSPRNG, you're more likely to know that your algorithm is correct, and that you're getting good, random results. If you later profile your code and see that the CSPRNG is a bottleneck, you can swap it out with something faster. And then you'll also have a baseline for comparison, so you'll know if using a weaker PRNG actually has a negative impact on whatever it is you're doing.
(And even if you don't do that profiling, you can swap out the CSPRNG just to see what happens, and get a good idea if the quality of the randomness produced by the PRNG is good enough, based on your experience with the CSPRNG.)