💻 Run new benchmarks

[JuaniRios]

What?

• Run the added benchmarks on AWS and put them on the pallet and runtime weight files
• hrmp benches ended up being lower than assumed XCM constant, so we're safe there.

How?

• Created a new just file to benchmark only certain extrinsics called benchmark-extrinsics

Anything Else?

• I saw that the only difference between the pallet and runtime benchmark configurations in our just-file are the flags

--no-storage-info \
--no-median-slopes \
--no-min-squares \

And those ones only seem to be affecting the print to console and not the actual benchmarking, so I copy-pasted the generated weights to both the pallet and runtime files

[JuaniRios]

• 💻 Run new benchmarks #352 👈
• 🧪 Experiment hrmp weighing #351
• ✨ New CT Migration benchmarks #346
• 👨🏻‍💻 Reorg extrinsics #345
• ✨ Multiple migration paths #341
• 💀 Add real weights to extrinsics #344
• main

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

Join @JuaniRios and the rest of your teammates on Graphite

[graphite-app]

Graphite Automations

"Auto-assign PRs to author" took an action on this PR • (07/05/24)

1 assignee was added to this PR based on Juan Ignacio Rios's automation.

[vstam1]

Quickly skimmed the weights, and they look good. Only question I still have is around this do_handle_channel_* benchmarks. I'm not sure if it would work like this.

[JuaniRios]

@vstam1

not sure if it would work like this.

Could you elaborate more what you meant?

[vstam1]

Related to the question in the prev PR. Can continue 'discussion' there

[JuaniRios]

Merge activity

• Jul 8, 8:35 AM EDT: @JuaniRios started a stack merge that includes this pull request via Graphite.
• Jul 8, 8:44 AM EDT: Graphite rebased this pull request as part of a merge.
• Jul 8, 8:45 AM EDT: @JuaniRios merged this pull request with Graphite.