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

[TASK] Update benchmarks and use proper weights #12

Closed
4 of 5 tasks
1xstj opened this issue Jun 1, 2022 · 0 comments · Fixed by #25
Closed
4 of 5 tasks

[TASK] Update benchmarks and use proper weights #12

1xstj opened this issue Jun 1, 2022 · 0 comments · Fixed by #25

Comments

@1xstj
Copy link
Contributor

1xstj commented Jun 1, 2022

Overview

The runtime is using default weights for many pallets, it would be ideal to write benchmarks for these pallets and execute benchmarks to generate weights that make sense for our parachain.

Use runtime benchmarking to ensure that the runtime weights are actually indicative of the resources used by the runtime.

Custom weights
If we need to diverge from benchmarks, make sure that each pallet in the runtime employs the correct weighting system.

Set block weight limit
It is recommended to have a block weight limit (block production time) of 0.5 seconds in the beginning due to uncertainties in block execution time. As the execution time of the network stabilizes the weight limit can be increased to 2 seconds.

Tasks

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

Successfully merging a pull request may close this issue.

2 participants