frequency icon indicating copy to clipboard operation
frequency copied to clipboard

Chore: use parametric variability in claim_staking_rewards benchmark, see if extrinsic can be optimized.

Open shannonwells opened this issue 7 months ago • 0 comments

Feature Description

Details

claim_staking_reward worst case is 95_000_000. Let's see if it can be improved at all.

Secondly the current benchmark measures worst case only. It needs to use a range of staking parameters so the weight isn't constantly overestimated.

Searched for Related Issues

  • [X] I have done a search for related issues and either found none, or noted them

shannonwells avatar Jul 17 '24 17:07 shannonwells