DO NOT MERGE: perf regression test

[camc314]

i am testing to see why perf dropped so much in #6424

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “0-merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link.

[camc314]

• DO NOT MERGE: perf regression test #6425 👈
• main

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

Join @camc314 and the rest of your teammates on Graphite

[codspeed-hq]

CodSpeed Performance Report

Merging #6425 will degrade performances by 12.93%

_{Comparing c/10-10-do_not_merge_perf_test (fee1156) with main (6a194f9)}

Summary

❌ 3 regressions
✅ 26 untouched benchmarks

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

Benchmarks breakdown

	Benchmark	main	c/10-10-do_not_merge_perf_test	Change
❌	minifier[antd.js]	349.6 ms	401.6 ms	-12.93%
❌	minifier[react.development.js]	2.5 ms	2.8 ms	-10.75%
❌	minifier[typescript.js]	452.4 ms	513.2 ms	-11.86%