🐛 [RUM-8353] Throttle view context update

[cy-moi]

Motivation

Updating of view context automatically triggers view updates, which could trigger excessive requests in edge cases. We should throttle view updates while maintaining current view context update behavior.

Changes

Added a new LifeCycleEvent type so we can update the view context for in viewHistory immediately
Use scheduleViewUpdate to throttle the view updates

Testing

• Local
• Staging
• Unit
• End to end

---

I have gone over the contributing documentation.

[cy-moi]

/to-staging

[dd-devflow]

Devflow running: /to-staging

View all feedbacks in Devflow UI.

---

2025-02-03 10:59:41 UTC ℹ️ Branch Integration: starting soon, median merge time is 0s

Commit a5e9c230bb will soon be integrated into staging-06.

---

2025-02-03 11:11:05 UTC ℹ️ Branch Integration: This commit was successfully integrated

Commit a5e9c230bb has been merged into staging-06 in merge commit 5e6fa9a836.

Check out the triggered pipeline on Gitlab 🦊

If you need to revert this integration, you can use the following command: /code revert-integration -b staging-06

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.59%. Comparing base (46cc11a) to head (4ac34a3).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3314   +/-   ##
=======================================
  Coverage   93.58%   93.59%           
=======================================
  Files         291      291           
  Lines        7691     7703   +12     
  Branches     1751     1751           
=======================================
+ Hits         7198     7210   +12     
  Misses        493      493           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cit-pr-commenter]

Bundles Sizes Evolution

📦 Bundle Name	Base Size	Local Size	𝚫	𝚫%	Status
Rum	146.77 KiB	147.05 KiB	279 B	+0.19%	✅
Logs	51.19 KiB	51.19 KiB	0 B	0.00%	✅
Rum Slim	105.52 KiB	105.77 KiB	254 B	+0.24%	✅
Worker	24.50 KiB	24.50 KiB	0 B	0.00%	✅

🚀 CPU Performance

Action Name	Base Average Cpu Time (ms)	Local Average Cpu Time (ms)	𝚫
addglobalcontext	0.002	0.002	-0.000
addaction	0.031	0.037	0.005
addtiming	0.006	0.001	-0.005
adderror	0.028	0.051	0.022
startstopsessionreplayrecording	0.001	0.012	0.011
startview	0.007	0.391	0.384
logmessage	0.025	0.021	-0.004

🧠 Memory Performance

Action Name	Base Consumption Memory (bytes)	Local Consumption Memory (bytes)	𝚫 (bytes)
addglobalcontext	28.15 KiB	27.95 KiB	-203 B
addaction	57.12 KiB	56.26 KiB	-874 B
addtiming	27.30 KiB	26.22 KiB	-1108 B
adderror	62.00 KiB	58.38 KiB	-3704 B
startstopsessionreplayrecording	25.50 KiB	25.37 KiB	-128 B
startview	415.29 KiB	422.12 KiB	6.83 KiB
logmessage	60.20 KiB	62.86 KiB	2.65 KiB

🔗 RealWorld

[amortemousque]

💬 suggestion: ‏I would expect BEFORE_VIEW_UPDATE to be called each time scheduleViewUpdate or triggerViewUpdate are called. Something like

  const { throttled, cancel: cancelScheduleViewUpdate } = throttle(triggerViewUpdate, THROTTLE_VIEW_UPDATE_PERIOD, {
    leading: false,
  })

  const scheduleViewUpdate = () => {
    triggerBeforeViewUpdate()
    throttled()
  }

 function triggerViewUpdate() {
    triggerBeforeViewUpdate()
    ...

[amortemousque]

💬 suggestion: ‏

Suggested change

	export interface ViewContextEvent {
	export interface BeforeViewUpdateEvent {

[thomas-lebeau]

💬 suggestion: ‏ Use THROTTLE_VIEW_UPDATE_PERIOD so we know where this value comes from and why we need it