-
Notifications
You must be signed in to change notification settings - Fork 152
2025 benchmark update #2024
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
Comments
As per the discussion on Zulip, we're going to wait a little bit and get some ducks lined up in a row before starting on this. |
This was referenced Apr 12, 2025
Merged
We have started the benchmark update process this week. |
This was referenced Apr 22, 2025
Merged
This was referenced Apr 30, 2025
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In 2025, it will be time to refresh and update our primary benchmarks again, based on our benchmark update policy.
The update policy, and a guide of how to actually update the benchmarks is described here. In short:
Cargo.lock
in the downloaded crate to git, even if it is ignored!perf-config.json
and.patch
files from the old version[workspace]
to Cargo.toml if it's not already thereworks
git diff --patch --relative
from the directory of the benchmark and store the output into the patch filename.collector/compile-benchmarks/README.md
collector/compile-benchmarks/REUSE.toml
bench_local
for both the old and the new benchmark version, then run the website locally (cargo run --bin site
), click on "Display raw data" and "Show non-relevant results" in the "Filters" section and post a screenshot of the results. Before running the benchmark, make sure to clear any stale benchmark data (rm results.db*
).Progress
clap_derive
4.5.32 (Add clap_derive 4.5.32 benchmark #2073, 28. 4.)cranelift-codegen-0.82.1
benchmark #2089)diesel-1.4.8
benchmark #2090)eza 0.21.2
(Addeza 0.21.2
benchmark #2084, 29. 4.)hyper
to 1.6.0 #2091, 30. 4.)typenum-1.18.0
benchmark #2088, 30. 4.)unicode-normalization-0.1.24
#2087, 30. 4.)webrender-2022
#2085)The text was updated successfully, but these errors were encountered: