You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ASV python benchmark configuration was removed a while ago (#46008, #49047), because we haven't been running those benchmarks the last years.
But the actual benchmarks itself were kept, and in light of #50398, I think we should get those running again, so we can at least run those benchmarks manually to assess the impact of the changes.
Yes, I know we have those benchmarks (see also our zulip chat about this in August), but those have a different (although somewhat overlapping) coverage.
The conbench ones are mostly about Parquet/Dataset (and some pandas.DataFrame -> pyarrow.Table conversion), while the ASV benchmarks also include basic python <-> arrow conversions (which is much more likely to be impacted by CPython C API usage changes).
Oh, I see. Also sorry I missed you meant ASV benchmarks.
I suppose you could reintroduce ASV or add new conbench benchmarks, whichever better serves your goals.
Please note there is an effort in progress to rewrite conbench (https://github.com/rok/benchx). The goal is to make benchmark authoring easier as well as making maintenance of benchmark store realistic.
Activity
rok commentedon Oct 9, 2026
To be honest I thought we did not have PyArrow benchmarks, however with some (🤖) searching:
arctosalliance/arrow-benchmarks-ci:
Group list with commands:
Benchmark implementations (arctosalliance/benchmarks):
Results can be seen here:
rok commentedon Oct 9, 2026
Please note - I did not design this system, I just maintain it :D
jorisvandenbossche commentedon Oct 12, 2026
Yes, I know we have those benchmarks (see also our zulip chat about this in August), but those have a different (although somewhat overlapping) coverage.
The conbench ones are mostly about Parquet/Dataset (and some pandas.DataFrame -> pyarrow.Table conversion), while the ASV benchmarks also include basic python <-> arrow conversions (which is much more likely to be impacted by CPython C API usage changes).
rok commentedon Oct 13, 2026
Oh, I see. Also sorry I missed you meant ASV benchmarks.
I suppose you could reintroduce ASV or add new conbench benchmarks, whichever better serves your goals.
Please note there is an effort in progress to rewrite conbench (https://github.com/rok/benchx). The goal is to make benchmark authoring easier as well as making maintenance of benchmark store realistic.