perf_hooks: add NODE_PERFORMANCE_GC_MINOR_MARK_SWEEP constant#63877
Merged
nodejs-github-bot merged 2 commits intoJun 23, 2026
Conversation
nodejs-github-bot
added
c++
BridgeAR
approved these changes
Jun 12, 2026
github-actions
Bot
removed
the
request-ci
Collaborator
legendecas
reviewed
Jun 12, 2026
| obs.observe({ entryTypes: ['gc'] }); | ||
|
|
||
| globalThis.gc({ type: 'minor' }); | ||
| // Keep the event loop alive to witness the GC async callback happen. |
Member
There was a problem hiding this comment.
Would you mind converting this to gcUntil from test/common/gc.js, reducing the flakiness on the gc timing?
This can be like:
let observed = fasel;
const obs = new PerformanceObserver(common.mustCallAtLeast((list) => {
...
observed = true;
}));
gcUntil('minor gc event', () => observed, 10, { type: 'minor' });
Contributor
Author
There was a problem hiding this comment.
That's a good suggestion – done; thanks!
anonrig
approved these changes
Jun 13, 2026
szegedi
force-pushed
the
feat/perf-hooks-gc-minor-mark-sweep
branch
from
35dac1a to
5caa3d0
Compare
Contributor
Author
|
force push merely amended the commit message to include the Signed-off-by trailer |
V8's Minor Mark-Sweep collector, enabled with the --minor-ms flag (available since Node.js 22), reports garbage collection performance entries with kind kGCTypeMinorMarkSweep (value 2). perf_hooks exposed constants for every other GC kind (major, minor, incremental, weakcb) but not this one, so consumers inspecting performanceEntry.detail.kind had no constant to compare against and saw an unmapped value. Expose it as perf_hooks.constants.NODE_PERFORMANCE_GC_MINOR_MARK_SWEEP, mirroring the existing v8::GCType mappings, and document it alongside the other GC kinds. Signed-off-by: Attila Szegedi <attila.szegedi@datadoghq.com>
szegedi
force-pushed
the
feat/perf-hooks-gc-minor-mark-sweep
branch
from
16d1ebc to
9880e42
Compare
IlyasShabi
approved these changes
Jun 15, 2026
Contributor
Author
|
There's one failing CI job (x86_64-linux: with shared libraries.) It looks unrelated to this change. It aborted in Looks like a flake/teardown issue. Could someone with the necessary permissions re-run the failed job (and/or kick off CI)? I don't have access to re-run it myself. Thanks! |
github-actions
Bot
removed
the
request-ci
Collaborator
legendecas
reviewed
Jun 15, 2026
| assert(entry); | ||
| assert.strictEqual(entry.name, 'gc'); | ||
| assert.strictEqual(entry.entryType, 'gc'); | ||
| assert.strictEqual(entry.detail.kind, NODE_PERFORMANCE_GC_MINOR_MARK_SWEEP); |
Member
There was a problem hiding this comment.
I think this callback could also be triggered by other minor GC types. This should be branched like:
if (entry.detail.kind === NODE_PERFORMANCE_GC_MINOR_MARK_SWEEP) {
observed = true;
}The CI failure seems to be that a scheduled GC fired before the forced NODE_PERFORMANCE_GC_FLAGS_FORCED.
Signed-off-by: Attila Szegedi <attila.szegedi@datadoghq.com>
szegedi
force-pushed
the
feat/perf-hooks-gc-minor-mark-sweep
branch
from
9880e42 to
4a6995c
Compare
legendecas
approved these changes
Jun 22, 2026
legendecas
added
perf_hooks
github-actions
Bot
removed
the
request-ci
Collaborator
Collaborator
legendecas
added
author ready
nodejs-github-bot
removed
the
commit-queue
Collaborator
|
Landed in 5075bb4 |
luanmuniz
pushed a commit
to luanmuniz/node
that referenced
this pull request
Jun 25, 2026
V8's Minor Mark-Sweep collector, enabled with the --minor-ms flag (available since Node.js 22), reports garbage collection performance entries with kind kGCTypeMinorMarkSweep (value 2). perf_hooks exposed constants for every other GC kind (major, minor, incremental, weakcb) but not this one, so consumers inspecting performanceEntry.detail.kind had no constant to compare against and saw an unmapped value. Expose it as perf_hooks.constants.NODE_PERFORMANCE_GC_MINOR_MARK_SWEEP, mirroring the existing v8::GCType mappings, and document it alongside the other GC kinds. Signed-off-by: Attila Szegedi <attila.szegedi@datadoghq.com> PR-URL: nodejs#63877 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Ilyas Shabi <ilyasshabi94@gmail.com> Reviewed-By: Chengzhong Wu <legendecas@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
V8's Minor Mark-Sweep collector (enabled with
--minor-ms, the default young-generation collector since V8 12.x / Node 22) reports garbage collection performance entries with kindkGCTypeMinorMarkSweep(value 2).perf_hooksexposed constants for every other GC kind (major, minor, incremental, weakcb) but not this one, so consumers inspectingperformanceEntry.detail.kindhad no constant to compare against and saw an unmapped value.With this PR I expose it as
perf_hooks.constants.NODE_PERFORMANCE_GC_MINOR_MARK_SWEEP, mirroring the existingv8::GCTypemappings, and document it alongside the other GC kinds.