Skip to content
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

[CI] Benchmark multiple runtimes at once #1052

Closed
Dinonard opened this issue Oct 11, 2023 · 0 comments · Fixed by #1060
Closed

[CI] Benchmark multiple runtimes at once #1052

Dinonard opened this issue Oct 11, 2023 · 0 comments · Fixed by #1060
Assignees
Labels
ci This PR/Issue is related to the topic "CI"

Comments

@Dinonard
Copy link
Member

Description

Running benchmarks only allows user to specify one runtime at a time.
This is problematic if we want to benchmark all of them at once, since each trigger
will rebuild the entire binary which takes time.

To improve this, suggestion is to change

# [chain name] - astar-dev, shiden-dev, shibuya-dev, dev
# [pallet names] - Use "," for multiple pallets, "all" for all pallets
/bench [chain name] [pallet names]

into

# [chain names] - Use "," for multiple runtimes. Available values are: astar-dev, shiden-dev, shibuya-dev, dev
# [pallet names] - Use "," for multiple pallets, "all" for all pallets
/bench [chain names] [pallet names]

The results should ideally be grouped in folders, according to their runtime.

@mc2eqe mc2eqe self-assigned this Oct 11, 2023
@mc2eqe mc2eqe added the ci This PR/Issue is related to the topic "CI" label Oct 17, 2023
@mc2eqe mc2eqe linked a pull request Oct 17, 2023 that will close this issue
5 tasks
@mc2eqe mc2eqe closed this as completed Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci This PR/Issue is related to the topic "CI"
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants