Skip to content
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

Writing intermediate results #306

Closed
wenkokke opened this issue Jul 1, 2020 · 8 comments · Fixed by #339
Closed

Writing intermediate results #306

wenkokke opened this issue Jul 1, 2020 · 8 comments · Fixed by #339
Labels

Comments

@wenkokke
Copy link

wenkokke commented Jul 1, 2020

Is there currently any way to force hyperfine to write intermediate results, so that I can abort a benchmark without losing all the progress I've made so far? I'm asking, because I've been benchmarking several algorithms with exponential complexity recently, and so sometimes letting the benchmark finish isn't an option.

@sharkdp
Copy link
Owner

sharkdp commented Aug 1, 2020

Are you talking about the --export … options?

There is no option like this, so far.

@wenkokke
Copy link
Author

wenkokke commented Aug 2, 2020

Yeah, I'm requesting that the --export options (at least the JSON and CSV options) write results to the file as soon as they become available, instead of at the end of the entire benchmark suite.

@sharkdp
Copy link
Owner

sharkdp commented Aug 2, 2020

Sounds like a good idea to me 👍

@BaronVonDrew
Copy link

@sharkdp Hey, I'd love to pick this up and add an 'incremental export' option if you don't mind? I'm fairly new to Rust but think I can give it a go

@sharkdp
Copy link
Owner

sharkdp commented Aug 7, 2020

Sounds great!

@negge
Copy link

negge commented Sep 29, 2020

Hi, I also ran into this issue recently on a long running benchmark. Do you know when this will be landing?

On a related note, please confirm that the target file is writable before invoking the test.

@sharkdp
Copy link
Owner

sharkdp commented Oct 13, 2020

On a related note, please confirm that the target file is writable before invoking the test.

you mean.. before running the first (potentially long-running) benchmark? That sounds like a good idea!

@sharkdp
Copy link
Owner

sharkdp commented Oct 17, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants