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

Benchmarks Issues #2181

Open
wilwade opened this issue Oct 10, 2024 · 3 comments
Open

Benchmarks Issues #2181

wilwade opened this issue Oct 10, 2024 · 3 comments

Comments

@wilwade
Copy link
Collaborator

wilwade commented Oct 10, 2024

Came across some issues with how we are running benchmarks with @enddynayn

  1. The frequency-bench chain is enabled for the frequency feature, but should only be enabled for runtime-benchmarks feature
  2. When we are running the benchmarks in run_benchmarks.sh it is running with features=runtime-benchmarks,frequency-lint-check. Should it instead be running with features=runtime-benchmarks,frequency?
    • Would this cause issues with non-mainnet pallets?
    • Perhaps it should run this way for release only?
  3. node/service/src/chain_spec/frequency.rs benchmark_mainnet_config should be limited to the runtime-benchmarks feature
@wilwade
Copy link
Collaborator Author

wilwade commented Oct 10, 2024

@aramikm can you verify that these are correct actions from your knowledge?

@aramikm
Copy link
Collaborator

aramikm commented Oct 10, 2024

Looks fine to me. One other thing to consider is that we run benchmarks 2 ways

  1. As release to generate correct weights
  2. As tests (when writing and debugging)

The 2nd use-case should also be taken care of if not already.

@aramikm
Copy link
Collaborator

aramikm commented Oct 10, 2024

Aside form pallets inclusion or exclusion, using frequency feature or not would have effect if we have feature based logic in our pallets that might alter the weight of benchmarks. I don't think we have anything like that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants