✨[RUM-3798] Report the cpu impact as a pr comment

[RomanGaignault]

Motivation

We want to know how much the Browser SDK is impacting the performances, and detect regressions early.

Changes

Using synthetic test we trigger a micro benchmark of actions you can perform on the sdk, measure the time used and retrieves data using logs2metrics.

Note : the S3 bucket contains now every built bundle of each PR. As it replaces the previous one after CI (for the same PR), only the built files for last commit before merging will be kept.

Testing

• Local
• Staging
• Unit
• End to end

---

I have gone over the contributing documentation.

[cit-pr-commenter]

Bundles Sizes Evolution

📦 Bundle Name	Base Size	Local Size	𝚫	𝚫%	Status
Rum	156.37 KiB	156.37 KiB	0 B	0.00%	✅
Logs	55.34 KiB	55.34 KiB	0 B	0.00%	✅
Rum Slim	102.86 KiB	102.86 KiB	0 B	0.00%	✅
Worker	25.21 KiB	25.21 KiB	0 B	0.00%	✅

🚀 CPU Performance

Action Name	Base Average Cpu Time (ms)	Local Average Cpu Time (ms)	𝚫
adderror	N/A	0.040	0.040
addaction	N/A	0.016	0.016
logmessage	N/A	0.006	0.006
startview	N/A	1.313	1.313
startstopsessionreplayrecording	N/A	1.043	1.043
addtiming	N/A	0.001	0.001
addglobalcontext	N/A	0.001	0.001

[RomanGaignault]

/to-staging

[dd-devflow]

🚂 Branch Integration: starting soon, merge in < 0s

Commit 6fa3e7acc0 will soon be integrated into staging-16.

This build is going to start soon! (estimated merge in less than 0s)

Use /to-staging -c to cancel this operation!

[dd-devflow]

🚨 Branch Integration: The build pipeline contains failing jobs for this merge request

We couldn't automatically merge the commit 6fa3e7acc0 into staging-16.
Build pipeline has failing jobs for df7e7e5

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected before the end of the pipeline.

You should have a look at the pipeline, wait for the build to finish and investigate the failures.
When you are ready, re-add your pull request to the queue!

⚠️ Do NOT retry failed jobs directly.

They were executed on a temporary branch created by the merge queue. If you retry them, they are going to fail because the branch no longer exists.

If you think the errors come from a logical conflict with the target branch, you can create a fix by commenting this pull request with /create-fix-branch -b staging-16

Details

List of failed jobs:

• test-performance

Go to failed Gitlab pipeline.

If you need support, contact us on Slack #devflow with those details!