-
Notifications
You must be signed in to change notification settings - Fork 312
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
Update weights from new benchmarks #2547
Conversation
//! WORST CASE MAP SIZE: `1000000` | ||
//! HOSTNAME: `ip-10-0-0-176`, CPU: `Intel(R) Xeon(R) Platinum 8375C CPU @ 2.90GHz` | ||
//! EXECUTION: None, WASM-EXECUTION: Compiled, CHAIN: Some("moonbase-dev"), DB CACHE: 1024 | ||
//! WASM-EXECUTION: `Compiled`, CHAIN: `Some("moonbase-dev")`, DB CACHE: 1024 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see it was using EXECUTION: None
before, I suspect it was wasm
and not native
@notlesh right ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, I think this is because the CLI options are ignored for wasm-execution now. But it hasn't made a difference in my testing...
the traits were removed by the automatic benchmarking
the change in weight is negligible but it has collateral effects for test execution
What does it do?
Generates weights for the runtime. Uses the ./scripts/run-benches-for-runtime.sh adapted from polkadot's. Each pallet has its own weight file that contains a generated trait WeightInfo as per the included template. Upon running the run-benches-for-runtime.sh the default template is used which merely implements the WeightInfo from the respective pallet's own weights.rs module, with the values for the current runtime.
The current PR uses weights generated by the benchmarking server, so is production-ready.
What important points reviewers should know?
Is there something left for follow-up PRs?
What alternative implementations were considered?
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
What value does it bring to the blockchain users?