Repository navigation
Contextual and GC friendly perf_hooks user timing #42503
Description
What is the problem this feature will solve?
Currently, it’s hard to manage GC lifetimes of user-timing entries without clearing all of them. Also, entries are identified by their names and types (marks or measures) to compute duration, thus it is quite easy for libraries to step on other's ways when using the perf_hooks.performance API.
The problem is more outstanding when using the perf_hooks.performance API in server environments, as the performance entries are going to be created again and again with the same name and are hard to manage in the global performance timeline.
What is the feature you are proposing to solve the problem?
As discussed at W3C PerfWG w3c/user-timing#86 (comment), there are interests in adding namespace support in the user-timing API.
With namespaces, performance entries could be all released at once when the namespace is no longer been used.
Opening this issue to gather visibility and feedback on the idea of w3c/user-timing#86.
/cc @jasnell
Activity
github-actions commentedon Jun 25, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 26, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.