Add a reusable benchmark harness for performance-sensitive changes

[hhhizzz]

Search before asking

• I searched in the issues and found nothing similar.

Motivation

Description

Currently, paimon-rust does not seem to have a reusable benchmark harness, such as cargo bench targets or a benchmark dev-dependency like Criterion.

I searched existing issues and did not find a general issue for introducing benchmark infrastructure. There are several performance-sensitive changes or discussions where benchmark evidence would be useful:

• feat: add custom Avro OCF reader for manifest parsing with filtered decoding #281 included ad-hoc “Benchmark for TableScan” results in the PR description.
• perf(reader): Improve the performance of parquet reader #230 improved Parquet reader performance.
• feat: Implement statistics for data fusion scan #217 added statistics for DataFusion scan to improve query performance.
• feat: Support Mosaic file format in paimon-rust #378 mentions future performance benchmarks for Mosaic after read compatibility becomes stable.

These examples suggest that benchmarks would help reviewers and contributors evaluate performance-sensitive PRs more consistently. However, without a reusable benchmark setup, performance comparisons are hard to reproduce and are usually left as one-off measurements in PR descriptions.

Would the project be open to adding a benchmark dependency and an initial set of cargo bench benchmarks?

This would not need to define final project-wide benchmark policy immediately. It could start as a small, reproducible benchmark harness and evolve as more performance-sensitive areas need coverage.

Solution

No response

Anything else?

No response

Willingness to contribute

• I'm willing to submit a PR!