chore: run benchmarking utility in devnet environment

[maschad]

Fixes TS-639

• Closes Run Benchmarking utility in devnet environment #3138

Summary

This PR introduces devnet benchmarking on master builds, as well as blob transaction deployment testing.

Also previous benchmarking tests are now looped 10 times to have more consistent results.

Checklist

• All changes are covered by tests (or not applicable)
• All changes are documented (or not applicable)
• I reviewed the entire PR myself (preferably, on GH UI)
• I described all Breaking Changes (or there's none)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
create-fuels-template	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 1, 2024 3:59pm
fuels-template	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 1, 2024 3:59pm
ts-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 1, 2024 3:59pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
create-fuels-counter-example	⬜️ Ignored (Inspect)			Oct 1, 2024 3:59pm

[codspeed-hq]

CodSpeed Performance Report

Merging #3166 will improve performances by ×8.1

_{Comparing mc/test/add-benchmarks-devnet (38920e3) with master (b6a82bc)}

Summary

⚡ 2 improvements

🆕 16 new benchmarks
⁉️ 19 dropped benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	master	mc/test/add-benchmarks-devnet	Change
⁉️	should successfully execute a contract deploy	101.3 ms	N/A	N/A
🆕	should successfully execute a contract deploy (x10 times)	N/A	99.9 ms	N/A
🆕	should successfully execute a contract deploy as blobs	N/A	3.7 s	N/A
⁉️	should successfully execute a contract mint	95.1 ms	N/A	N/A
🆕	should successfully execute a contract mint (x10 times)	N/A	65.5 ms	N/A
⁉️	should successfully execute a contract multi call	71.7 ms	N/A	N/A
🆕	should successfully execute a contract multi call (x10 times)	N/A	72.1 ms	N/A
⁉️	should successfully execute a contract read function	67.8 ms	N/A	N/A
🆕	should successfully execute a contract read function (x10 times)	N/A	66.8 ms	N/A
⁉️	should successfully write to a contract	65.9 ms	N/A	N/A
🆕	should successfully write to a contract (x10 times)	N/A	65.4 ms	N/A
⁉️	should successfully get transaction cost estimate for a batch transfer	47.3 ms	N/A	N/A
🆕	should successfully get transaction cost estimate for a batch transfer (x10 times)	N/A	24.3 ms	N/A
🆕	should successfully get transaction cost estimate for a mint (x10 times)	N/A	21.7 ms	N/A
⁉️	should successfully get transaction cost estimate for a single contract call	22.6 ms	N/A	N/A
🆕	should successfully get transaction cost estimate for a single contract call (x10 times)	N/A	24.6 ms	N/A
⁉️	should successfully get transaction cost estimate for a single transfer	26.8 ms	N/A	N/A
🆕	should successfully get transaction cost estimate for a single transfer (x10 times)	N/A	18.4 ms	N/A
⁉️	should successfully get transaction cost estimate for multi contract calls	36 ms	N/A	N/A
🆕	should successfully get transaction cost estimate for multi contract calls (x10 times)	N/A	30.8 ms	N/A
...	...	...	...	...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

[petertonysmith94]

🔥

[petertonysmith94]

@maschad just a conflict with the pnpm-lock.yaml file here.

[petertonysmith94]

🔥