Skip to content

[stable2603] Backport #11069#11074

Merged
sigurpol merged 1 commit intostable2603from
backport-11069-to-stable2603
Feb 16, 2026
Merged

[stable2603] Backport #11069#11074
sigurpol merged 1 commit intostable2603from
backport-11069-to-stable2603

Conversation

@paritytech-release-backport-bot
Copy link
Copy Markdown

Backport #11069 into stable2603 from sigurpol.

See the documentation on how to use this bot.

Fix huge benchmark regression for storage-heavy extrinsics, enabling
jemalloc-allocator via polkadot-jemalloc-shim for omni-bencher, marked
as optional in the scope of PR #10590.

This close paritytech/trie#230.

Thanks @alexggh and @cheme for the help 🙇

Tested against `runtime / main` and
[2.1.0](polkadot-fellows/runtimes#1065) as
described
[here](paritytech/trie#230 (comment)).
For the `usual` exstrinsic `force_apply_min_commission` doing massive
storage allocation/deallocation on benchmark setup and then just 1read -
2 write in the benchmark extrinsic itself, times goes down from ms to
µs.

The regression was introduced by #10590 `sc-client-db: Make jemalloc
optional`

```bash
runtimes git:(sigurpol-release-2_0_6) /home/paolo/github/polkadot-sdk/target/release/frame-omni-bencher v1 benchmark pallet --runtime ./target/release/wbuild/asset-hub-polkadot-runtime/asset_hub_polkadot_runtime.compact.compressed.wasm --pallet pallet_staking_async --extrinsic "force_apply_min_commission" --steps 2 --repeat 1
2026-02-13T15:06:30.145367Z  INFO frame::benchmark::pallet: Initialized runtime log filter to 'INFO'
2026-02-13T15:06:31.784936Z  INFO pallet_collator_selection::pallet: assembling new collators for new session 0 at #0
2026-02-13T15:06:31.784966Z  INFO pallet_collator_selection::pallet: assembling new collators for new session 1 at #0
2026-02-13T15:08:29.701636Z  INFO frame::benchmark::pallet: [  0 % ] Starting benchmark: pallet_staking_async::force_apply_min_commission
2026-02-13T15:08:35.130403Z  INFO frame::benchmark::pallet: [  0 % ] Running  benchmark: pallet_staking_async::force_apply_min_commission (overtime)
Pallet: "pallet_staking_async", Extrinsic: "force_apply_min_commission", Lowest values: [], Highest values: [], Steps: 2, Repeat: 1
Raw Storage Info
========
Storage: `Staking::MinCommission` (r:1 w:0)
Proof: `Staking::MinCommission` (`max_values`: Some(1), `max_size`: Some(4), added: 499, mode: `MaxEncodedLen`)
Storage: `Staking::Validators` (r:1 w:1)
Proof: `Staking::Validators` (`max_values`: None, `max_size`: Some(45), added: 2520, mode: `MaxEncodedLen`)

Median Slopes Analysis
========
-- Extrinsic Time --

Model:
Time ~=    50.31
              µs

Reads = 2
Writes = 1
Recorded proof Size = 564

Min Squares Analysis
========
-- Extrinsic Time --

Model:
Time ~=    50.31
              µs

Reads = 2
Writes = 1
Recorded proof Size = 564
```

---------

Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Bastian Köcher <git@kchr.de>
(cherry picked from commit bc42349)
@paritytech-release-backport-bot paritytech-release-backport-bot Bot requested a review from a team as a code owner February 16, 2026 00:11
@github-actions github-actions Bot added the A3-backport Pull request is already reviewed well in another branch. label Feb 16, 2026
@github-actions github-actions Bot requested a review from sigurpol February 16, 2026 00:11
@github-actions
Copy link
Copy Markdown
Contributor

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

  • Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
  • Should be a legit fix for some bug, not adding tons of new features.
  • Must either be already audited or not need an audit.
Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.

@sigurpol sigurpol merged commit f6dd735 into stable2603 Feb 16, 2026
242 of 246 checks passed
@sigurpol sigurpol deleted the backport-11069-to-stable2603 branch February 16, 2026 08:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A3-backport Pull request is already reviewed well in another branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant