-
Notifications
You must be signed in to change notification settings - Fork 83
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
Automatically benchmark runtimes #1009
Comments
Example command to run the benchmarks for the kintsugi runtime and output those to a cargo run --bin interbtc-parachain --features runtime-benchmarks --release -- benchmark pallet --pallet '*' --extrinsic '*' --chain kintsugi-dev --execution=wasm --wasm-execution=compiled --steps 50 --repeat 20 --output parachain/runtime/kintsugi/src/weights/ --template .deploy/weight-template.hbs |
You need to use the new runtime-specific template, so e.g.
|
I also found these scripts used in polkadot which may be useful https://github.com/paritytech/polkadot/blob/master/scripts/ci/run_benches_for_runtime.sh https://github.com/paritytech/substrate/blob/master/scripts/run_all_benchmarks.sh |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need some tooling to automatically run our benchmarks and output the weights (see the kusama runtime structure for example). I'm not sure what the best approach is but I like Acala's setup so we can run the
/bench
command from the PR for an individual pallet or the entire runtime - although I'm not sure how these files are then committed. I took a brief look at Parity's setup and they seem to run the benchmarks elsewhere (I think GitLab) and commit the updated weights manually. Whatever solution we adopt I would like to have these run more frequently so we can catch breaking changes early - automatically running in PRs would be great but not sure if this would take too long.The text was updated successfully, but these errors were encountered: