-
-
Notifications
You must be signed in to change notification settings - Fork 382
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
Do not suggest usage of "--warmup" if already used #570
Comments
Not sure I get your point. Using
What does this mean?
Ah, hm. I haven't checked, but yeah: it might be the case that the warning can be shown even when I still think the warning is useful in general. |
usually, there is some spinning and output about what hyperfine is currently doing. So you can see it's doing the warmup, then it's doing the first test. You have information about the current average even if all the tests are not done. using tee I didn't see any of that. So I'm not 100% sure the warmup did happen even if I set the option. I agree with you that knowing that the first run was slower even if you use --warmup is important. it's just because it's already set. you get confused at "it is properly set up?". a spelling mistake or argument order can matter and be silently ignored. |
I can not confirm this.
clearly takes around four seconds, so warmup is being performed. |
Maybe try a longer warmup phase? |
The title of the issue is actually incorrect now because I understand better the problem. |
Thank you, you are the best |
I ran the following command to compare the performance of these two programs
I was surprised to see the following warning: "Warning: The first benchmarking run for this command was significantly slower than the rest (2928.564 s). This could be caused by (filesystem) caches that were not filled until after the first run. You should consider using the '--warmup' option to fill those caches before the actual benchmark. Alternatively, use the '--prepare' option to clear the caches before each timing run."
Usually, I don't use tee and I sew the warmup run on the output but using tee the output is way less verbose.
Does the warmup option has been ignored for some reason, or does this warning appear even if the option is set but the first run is slower?
The text was updated successfully, but these errors were encountered: