GH-39663: [C++] Ensure top-level benchmarks present informative metrics#40091
GH-39663: [C++] Ensure top-level benchmarks present informative metrics#40091pitrou merged 1 commit intoapache:mainfrom
Conversation
… metrics Add bytes/second and/or items/second metrics where applicable.
|
|
|
@ursabot please benchmark lang=C++ |
|
Benchmark runs are scheduled for commit c10547a. Watch https://buildkite.com/apache-arrow and https://conbench.ursa.dev for updates. A comment will be posted here when the runs are complete. |
|
Thanks for your patience. Conbench analyzed the 1 benchmarking run that has been run so far on PR commit c10547a. There were 2 benchmark results indicating a performance regression:
The full Conbench report has more details. |
|
After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit b224c58. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them. |
Rationale for this change
Some benchmarks may present only an iteration time, or not present sufficiently informative metrics.
What changes are included in this PR?
Add bytes/second and/or items/second metrics to top-level benchmarks where applicable.
This PR only tackles miscellaneous benchmarks from the top-level Arrow directory, as well as IO, IPC and utilities.
Are these changes tested?
Manually.
Are there any user-facing changes?
No.