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

Update weights from new benchmarks #2547

Merged
merged 7 commits into from
Nov 2, 2023
Merged

Conversation

noandrea
Copy link
Collaborator

@noandrea noandrea commented Oct 31, 2023

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?

@noandrea noandrea added B7-runtimenoteworthy Changes should be noted in any runtime-upgrade release notes D3-trivial PR contains trivial changes in a runtime directory that do not require an audit not-breaking Does not need to be mentioned in breaking changes labels Oct 31, 2023
@noandrea noandrea marked this pull request as ready for review October 31, 2023 21:11
//! 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
Copy link
Collaborator

@crystalin crystalin Oct 31, 2023

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 ?

Copy link
Contributor

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...

@librelois
Copy link
Collaborator

@noandrea this branch seem's to be based on an old version of master, before the merge of #2533, so your PR silently erase the addtional DB read for the call proxy.proxy, please re-add it

the change in weight is negligible but it has collateral effects
for test execution
@librelois librelois merged commit b4ebf71 into master Nov 2, 2023
27 of 28 checks passed
@librelois librelois deleted the noandrea-benchmarking-rt2600 branch November 2, 2023 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B7-runtimenoteworthy Changes should be noted in any runtime-upgrade release notes D3-trivial PR contains trivial changes in a runtime directory that do not require an audit not-breaking Does not need to be mentioned in breaking changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants