[C++] Top-level Arrow benchmarks should present a items/s or bytes/s metric #39663
Comments
7 tasks
pitrou
added a commit
to pitrou/arrow
that referenced
this issue
Feb 15, 2024
… metrics Add bytes/second and/or items/second metrics where applicable.
pitrou
added a commit
that referenced
this issue
Feb 19, 2024
…cs (#40091) ### 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: #39663 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
zanmato1984
pushed a commit
to zanmato1984/arrow
that referenced
this issue
Feb 28, 2024
… metrics (apache#40091) ### 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: apache#39663 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
thisisnic
pushed a commit
to thisisnic/arrow
that referenced
this issue
Mar 8, 2024
… metrics (apache#40091) ### 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: apache#39663 Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the enhancement requested
We should scan through these benchmarks and look for those that only a present an iteration time.
This includes benchmarks for utilities, tensors, IPC, the C Data Interface and (if possible) GPU support.
Component(s)
Benchmarking, C++
The text was updated successfully, but these errors were encountered: