From 56d89ab041bd8f30eb128648ba8fbe92526762dc Mon Sep 17 00:00:00 2001 From: Ignacio Palacios <ignacio.palacios.santos@gmail.com> Date: Thu, 3 Feb 2022 18:41:44 +0100 Subject: [PATCH] Update command for running benchmarks (#954) * Update command for running benchmarks * add --locked Co-authored-by: Chevdor <chevdor@users.noreply.github.com> Co-authored-by: Chevdor <chevdor@users.noreply.github.com> --- cumulus/.github/ISSUE_TEMPLATE/release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cumulus/.github/ISSUE_TEMPLATE/release.md b/cumulus/.github/ISSUE_TEMPLATE/release.md index 31321fddbd9..1cc8fb2de22 100644 --- a/cumulus/.github/ISSUE_TEMPLATE/release.md +++ b/cumulus/.github/ISSUE_TEMPLATE/release.md @@ -146,7 +146,7 @@ Until #631 is done, running the benchmarks is a manual process: 1. Connect to the bechmarking machine 2. Make sure no one else is using the machine with `htop check` 3. Pull in the branch of Cumulus that has the version of Statemine you want to release -4. Recompile `cargo build --release --features runtime-benchmarks` +4. Recompile `cargo build --profile production --locked --features runtime-benchmarks` 5. From the root directory run `nohup ./scripts/benchmarks.sh &` (it will take quite a few hours) 6. Checkout in your local machine to the branch of cumulus that has the version of Statemine you want to release 7. `scp` from the host to your local machine the weights for Statemine, Westmint and Statemint you'll find in: -- GitLab