🛠️ Rework benchmarks

[JuaniRios]

What?

• Fix and modify pallet-funding benchmarks post-simplification

Why?

• Our benchmarks were overtly complicated, a result of the old logic.

How?

• Fix syntax for new instantiator functions
• Simplify setup
• Delete old logic branches (e.g. no longer "unchanged" outcome for evaluator, no more benchmark for that)
• When 2 logic branches only had a small difference (e.g. 1 storage read/write), we now benchmark the worst case.

Testing?

cargo test --features runtime-benchmarks just dry-run-benchmarks Keep in mind you need to do a cargo clean for it to work (dunno why)

Anything Else?

Had to delete the runtime weights since the weight struct looks different. The runtime now uses the default () from the new weight file I generated in the pallet.

Soon we will generate the real pallet/runtime benchmarks in AWS

[JuaniRios]

• #376 : 3 dependent PRs (#375 , #379 , #380 )
• #374 👈
• #377
• #372
• #373
• #371
• #369
• #368
• #365
• #367
• #366
• #364 : 1 other dependent PR (#370 )
• #363
• #362
• #361
• #358
• #354
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JuaniRios and the rest of your teammates on Graphite

[JuaniRios]

Merge activity

• Aug 23, 5:56 AM EDT: @JuaniRios started a stack merge that includes this pull request via Graphite.
• Aug 23, 6:47 AM EDT: Graphite rebased this pull request as part of a merge.
• Aug 23, 6:48 AM EDT: @JuaniRios merged this pull request with Graphite.