GH-39663: [C++] Ensure top-level benchmarks present informative metrics

[pitrou]

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.

• Closes: [C++] Top-level Arrow benchmarks should present a items/s or bytes/s metric #39663

[github-actions]

⚠️ GitHub issue #39663 has been automatically assigned in GitHub to PR creator.

[pitrou]

@ursabot please benchmark lang=C++

[ursabot]

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.

[conbench-apache-arrow]

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:

• Pull Request Run on ursa-thinkcentre-m75q at 2024-02-15 11:23:17Z
  • ShortVectorInsertAtEnd (C++) with params=<STATIC_VECTOR(int)>, source=cpp-micro, suite=arrow-small-vector-benchmark
  • BuildAdaptiveIntNoNullsScalarAppend (C++) with source=cpp-micro, suite=arrow-builder-benchmark

The full Conbench report has more details.

[kou]

+1

[conbench-apache-arrow]

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.