election-provider-multi-block: reduce overclaimed proof_size during Signed phase#11156
Merged
sigurpol merged 2 commits intoFeb 24, 2026
Merged
Conversation
…igned phase on_initialize claimed on_initialize_into_signed weight (> ~3M proof_size) every block during the Signed phase, but the heavy work (loading voter snapshots) only happens once when transitioning from Snapshot into Signed. Use discriminant comparison to distinguish phase entry from same-phase ticks, falling back to on_initialize_nothing for the latter.
Contributor
Author
|
/cmd prdoc --audience runtime_dev --bump |
Contributor
|
This pull request is amending an existing release. Please proceed with extreme caution,
Emergency Bypass
If you really need to bypass this check: add |
Contributor
Author
|
/cmd prdoc --audience runtime_dev --bump patch |
…time_dev --bump patch'
Contributor
Author
|
This is meant to be a tentative workaround for #11034 for Release 2.1.0 based on 2512 where due to lack of time, we can't afford to backport #9925 . The expected benefit is that only during Snapshot phase (33 blocks) and in the transition Snapshot(0 ) -> Signed(N) we would see a spike in PoV but after that, Signed(_) is back to normal since no heavy work is performed |
kianenigma
approved these changes
Feb 24, 2026
sigurpol
deleted the
sigurpol-election-poll-reduce-weight-for-signed-phase
branch
EgorPopelyaev
added a commit
that referenced
this pull request
Feb 25, 2026
fellowship-merge-bot Bot
pushed a commit
to polkadot-fellows/runtimes
that referenced
this pull request
Feb 26, 2026
- Bump election provider multiblock to include [SDK PR#11156](paritytech/polkadot-sdk#11156) : reduce overclaimed proof_size during Signed phase - Bump staking pallets to include [SDK PR#11168](paritytech/polkadot-sdk#11168): add a configurable MinSetKeysBond threshold that rejects set_keys when active bond is insufficient.
arturgontijo
pushed a commit
to moonbeam-foundation/polkadot-sdk
that referenced
this pull request
Apr 1, 2026
…igned phase (paritytech#11156) on_initialize claimed on_initialize_into_signed weight (> ~3M proof_size) every block during the Signed phase, but the heavy work (loading voter snapshots) only happens once when transitioning from Snapshot into Signed. Use discriminant comparison to distinguish phase entry from same-phase ticks, falling back to on_initialize_nothing for the latter. A proper fix would be backporting paritytech#9925 into stable2512 - but this would be a bigger change not compatible with the tight timeline of 2.1.0 release on Polkadot/Kusama. --------- Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
arturgontijo
pushed a commit
to moonbeam-foundation/polkadot-sdk
that referenced
this pull request
Apr 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
on_initialize claimed on_initialize_into_signed weight (> ~3M proof_size) every block during the Signed phase, but the heavy work (loading voter snapshots) only happens once when transitioning from Snapshot into Signed.
Use discriminant comparison to distinguish phase entry from same-phase ticks, falling back to on_initialize_nothing for the latter.
A proper fix would be backporting #9925 into stable2512 - but this would be a bigger change not compatible with the tight timeline of 2.1.0 release on Polkadot/Kusama.