-
Notifications
You must be signed in to change notification settings - Fork 335
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
Weights per runtime #3019
base: master
Are you sure you want to change the base?
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: 2228 KB (no changes) ✅ Moonriver runtime: 2232 KB (no changes) ✅ Compared to latest release (runtime-3300)Moonbase runtime: 2260 KB (+232 KB compared to latest release) Moonbeam runtime: 2228 KB (+232 KB compared to latest release) Moonriver runtime: 2232 KB (+240 KB compared to latest release) |
Coverage Report@@ Coverage Diff @@
## master gonza/weights-per-runtime +/- ##
=============================================================
- Coverage 79.00% 74.57% -4.43%
+ Files 303 371 +68
+ Lines 88208 94433 +6225
=============================================================
+ Hits 69685 70421 +736
+ Misses 18523 24012 +5489
|
|
…untime # Conflicts: # runtime/moonbase/src/weights/pallet_moonbeam_lazy_migrations.rs
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. |
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?