We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In 2025, it will be time to refresh and update our benchmarks again, based on our benchmark update policy.
We expect to start the update in spring 2025.
The update policy, and a guide of how to actually update the benchmarks is described here. In short:
$ cargo run --bin collector download -c Primary -a <library/binary> crate <name> <version>
perf-config.json
.patch
[workspace]
collector/compile-benchmarks/README.md
collector/compile-benchmarks/REUSE.toml
time -p CARGO_INCREMENTAL=0 cargo check ; cargo clean time -p CARGO_INCREMENTAL=0 cargo build ; cargo clean time -p CARGO_INCREMENTAL=0 cargo build --release ; cargo clean
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
No branches or pull requests
In 2025, it will be time to refresh and update our benchmarks again, based on our benchmark update policy.
We expect to start the update in spring 2025.
The update policy, and a guide of how to actually update the benchmarks is described here. In short:
perf-config.json
and.patch
files from the old version[workspace]
to Cargo.toml if it's not already therecollector/compile-benchmarks/README.md
collector/compile-benchmarks/REUSE.toml
The text was updated successfully, but these errors were encountered: