-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Micro benchmark regularly and display benchmark result #25754
Comments
The performance regression by such kind of changes should be captured by the micro benchmark tikv/client-go#145 |
And the point get query performance regression like this one #25573 |
The data is still generated manually, because I want to make sure it works, proof of concept Later, I'll make it run automatically. |
B.T.W, golang also have a page about perf https://perf.golang.org/, but I dislike it. It's not visualized. |
The data of the last few months is now available here http://www.zenlife.tk:18081/ |
@tiancaiamao Could you locate the PR/commit that introduces this regression? |
|
Feature Request
Is your feature request related to a problem? Please describe:
We do not use the benchmark well.
Benchmarks can guide us the evaluation of the product performance.
But they are too high level.
Describe the feature you'd like:
I'd like to have some micro benchmarks and run them regularly.
For example, if we have a
make bench
command to run the micro benchmarks, and the result is collected,and visualized, then we know the performance regression early.
Describe alternatives you've considered:
For example, there is a scheme benchmark website, https://ecraven.github.io/r7rs-benchmarks/
From which we can see the performance between different scheme compile implementation easily.
Another example is the rust pref https://perf.rust-lang.org/
I'd like TiDB to have something similar, there are may micro benchmarks and the result can be compared by day.
Teachability, Documentation, Adoption, Migration Strategy:
The text was updated successfully, but these errors were encountered: