♻️ Replace longTaskRegistry by longTaskContexts

[amortemousque]

Motivation

Remove longTaskRegistry and use a new longTaskContext exposed by longTaskCollection. This keeps the codebase consistent and preserves the bundle size.

Changes

• Move longAnimationFrameCollection into longTaskCollection, since long tasks act as the fallback for LOAF.
• Expose longTaskContexts from longTaskCollection.
• Replace longTaskRegistry with longTaskContexts in profiling.
• Delete longTaskRegistry and profilingCorrelation modules.

Checklist

• Tested locally
• Tested on staging
• Added unit tests for this change.
• Added e2e/integration tests for this change.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[datadog-datadog-prod-us1]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage
• Patch Coverage: 100.00%
• Total Coverage: 92.68% (+0.05%)

View detailed report

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 847e3b4 | Docs | Datadog PR Page | Was this helpful? Give us feedback!}

[cit-pr-commenter]

Bundles Sizes Evolution

📦 Bundle Name	Base Size	Local Size	𝚫	𝚫%	Status
Rum	164.30 KiB	164.32 KiB	+17 B	+0.01%	✅
Rum Profiler	5.21 KiB	4.32 KiB	-909 B	-17.05%	✅
Rum Recorder	19.74 KiB	19.74 KiB	+1 B	+0.00%	✅
Logs	56.14 KiB	56.14 KiB	0 B	0.00%	✅
Flagging	944 B	944 B	0 B	0.00%	✅
Rum Slim	121.57 KiB	121.60 KiB	+33 B	+0.03%	✅
Worker	23.63 KiB	23.63 KiB	0 B	0.00%	✅

🚀 CPU Performance

Action Name	Base CPU Time (ms)	Local CPU Time (ms)	𝚫%
RUM - add global context	0.0058	0.0041	-29.31%
RUM - add action	0.0175	0.0126	-28.00%
RUM - add error	0.0159	0.0133	-16.35%
RUM - add timing	0.0045	0.0038	-15.56%
RUM - start view	0.005	0.0036	-28.00%
RUM - start/stop session replay recording	0.0012	0.0009	-25.00%
Logs - log message	0.0218	0.0194	-11.01%

🧠 Memory Performance

Action Name	Base Memory Consumption	Local Memory Consumption	𝚫
RUM - add global context	25.94 KiB	25.27 KiB	-691 B
RUM - add action	49.52 KiB	48.23 KiB	-1.30 KiB
RUM - add timing	24.32 KiB	24.35 KiB	+37 B
RUM - add error	54.73 KiB	53.41 KiB	-1.32 KiB
RUM - start/stop session replay recording	23.65 KiB	23.94 KiB	+299 B
RUM - start view	424.60 KiB	425.47 KiB	+885 B
Logs - log message	43.70 KiB	44.27 KiB	+591 B

🔗 RealWorld

[amortemousque]

Unrelated but use classic function declaration for consistency

[thomasbertet]

LGTM overall !

Added a nit on naming, but otherwise I believe that's a great refactoring!

[thomasbertet]

Is this s plural to represent the API object a convention ? Otherwise I can suggest :

export interface LongTaskEntry {
  id: string
  startClocks: ClocksState
  duration: Duration
  entryType: RumPerformanceEntryType.LONG_ANIMATION_FRAME | RumPerformanceEntryType.LONG_TASK
}

and

export interface LongTaskContext {
  findLongTasks: (startTime: RelativeTime) => LongTaskEntry[]
}

I'd find this a bit more clear - but it may not be following existing convention so overall I trust what you think is best !

[amortemousque]

/to-staging

[dd-devflow-routing-codex]

View all feedbacks in Devflow UI.

2025-12-12 08:40:06 UTC ℹ️ Start processing command /to-staging

---

2025-12-12 08:40:14 UTC ℹ️ Branch Integration: starting soon, merge expected in approximately 0s (p90)

Commit 847e3b43d6 will soon be integrated into staging-50.

---

2025-12-12 08:56:24 UTC ℹ️ Branch Integration: this commit was successfully integrated

Commit 847e3b43d6 has been merged into staging-50 in merge commit 14ec0770a2.

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-50