-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Improve benchmark documentation #15054
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
Improve benchmark documentation #15054
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you as always @carols10cents 🙏
The output of `dfbench` help includes a description of each benchmark, which is reproduced here for convenience | ||
The output of `dfbench` help includes a description of each benchmark, which is reproduced here for convenience. | ||
|
||
## Cancellation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
@@ -97,7 +100,7 @@ impl RunOpt { | |||
println!("Done loading data into in-memory object store"); | |||
|
|||
let mut rundata = BenchmarkRun::new(); | |||
rundata.start_new_case("Arglebargle"); | |||
rundata.start_new_case("Cancellation"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤦 -- sorry about that.
Though today I have learned a new placeholder word!
Thanks again @carols10cents |
* Replace placeholder with a more appropriate benchmark title * Clarify purpose of this benchmark * Add cancellation benchmark to benchmarks README
Which issue does this PR close?
This is a follow-on to #14818.
Rationale for this change
There were some further improvements to the documentation that @alamb and I noticed after #14818 was merged in.
What changes are included in this PR?
I noticed there was a label with the text "Arglebargle" that I put in there before I knew where that text ended up (it's a heading in the
bench.sh
output)@alamb had a suggestion in the previous PR that I've now taken
In my next PR, @alamb noticed I forgot to add this benchmark's description to
benchmarks/README.md
Are these changes tested?
Nope, they're just docs :)
Are there any user-facing changes?
These are the docs :)