-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Weights per runtime #3019
Weights per runtime #3019
Conversation
…r-runtime # Conflicts: # runtime/common/src/lib.rs # runtime/moonbase/src/weights/pallet_xcm_weight_trader.rs # runtime/moonbeam/src/lib.rs # runtime/moonbeam/src/precompiles.rs # runtime/moonriver/src/precompiles.rs
WASM runtime size check:Compared to target branchMoonbase runtime: 2260 KB (no changes) ✅ Moonbeam runtime: 2224 KB (no changes) ✅ Moonriver runtime: 2224 KB (no changes) ✅ Compared to latest release (runtime-3300)Moonbase runtime: 2260 KB (+232 KB compared to latest release) Moonbeam runtime: 2224 KB (+228 KB compared to latest release) Moonriver runtime: 2224 KB (+232 KB compared to latest release) |
Coverage Report@@ Coverage Diff @@
## master gonza/weights-per-runtime +/- ##
=============================================================
- Coverage 79.34% 74.81% -4.53%
+ Files 301 369 +68
+ Lines 87834 94127 +6293
=============================================================
+ Hits 69685 70421 +736
+ Misses 18149 23706 +5557
|
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.
Changes in specs
should be reverted.
good catch, I don't know, maybe it was a bad merge. |
We should flag weights that are being changed by more than 10% so we can discuss their impacts |
Here the list of the changes greater than 5% . The negatives are improvements.
|
Btw, the comparison is against weights in moonbase (master). But the weights difference between moonbase (master) and moonbase (this branch) is negligible: in average |
The weight difference is now reasonable. Do you know why it was different before? |
What does it do?
This PR replaces #2939.
It modifies pallet's benchmarks and removes magic numbers to be runtime-dependant.
What important points reviewers should know?
Pallet parachain staking had some fixed numbers that I replaced by values we get from the runtime. This might go against the testing purpose, because now a change on those parameters might go unnoticed in the test. Anyway I think it is an acceptable trade off.
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?