Skip to content

Use end to end microbenchmarks to prevent performance regressions between releases #5373

Description

@andygrove

What is the problem the feature request solves?

WE already have many microbenchmarks that test end to end performance of Spark vs Comet for operators and expressions, but they need some work (tracked in #5363).

I would like to add documentation on running these benchmarks and checking the results into the repo using a specific EC2 instance type so that anybody can reproduce them.

Perhaps we can eventually automate this to run on a regular schedule during development cycles between releases.

Describe the potential solution

No response

Additional context

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:ciCI/CD, GitHub Actions, build toolingenhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions