Skip to content

Add a reusable benchmark harness for performance-sensitive changes #483

Description

@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:

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions