-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DieHarder? And some results. #30
Comments
You need to give an argument to
Importantly, the benchmarks in the |
Sure. I think that it's just a matter of aligning the documentation with the cabal (v2) commands that you need to invoke to make things happen, and defocus all the JS stuff. It takes quite a bit of digging to discover that This all seems a bit single-threaded. Perhaps that is inherent, but if you are generating lots of randoms ... It's be good to have some settings that ran for 10m, rather than 30m |
I don't understand, what you mean |
I'll have a further poke, but is not the Are the options documented somewhere (perhaps in a source file)? And the |
|
Ah. That makes more sense! |
I wasn't able to figure out how to run die harder on this library (cabal-plan seems to be some javascript-related doobry) but here, for reference, are some results after adding
-O2 -fllvm
to theghc-options
in the cabal file.cabal test
, which I was expecting to do the diehard validation seems to complete v quickly (and successfully).And this is how fast die harder ran, for comparison.
The text was updated successfully, but these errors were encountered: