-
Notifications
You must be signed in to change notification settings - Fork 407
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
Benchmarks/timings are a little misleading #204
Comments
This undocumented reporting of CPU instead of real time also makes Argon2 appear to be faster than it actually is under the current system load - which is especially relevant when benchmarking multiple concurrent instances using a script around the supplied The program should say "seconds of CPU time" or the like (not just "seconds"), or alternatively the uses of |
This is because benchmark is using the Also see this: #368 |
@vault-thirteen No, that's a separate issue. This one is about the CPU time reporting vs. users' expectations of real time being reported. The readings for this are obtained from the OS, via |
Hi,
Just a note that currently the benchmark timings (and similarly the output of the CLI tool) are perhaps a bit confusing, by reporting the CPU time instead of wall.
This is probably intentional, but there could perhaps be a note somewhere, or an option to display both.
For example:
From which it appears as though it takes longer with more threads. When the actual wall time is significantly shorter:
The text was updated successfully, but these errors were encountered: