From fe92fc68b62fc02e94c88f113d371b63e2ba6bf6 Mon Sep 17 00:00:00 2001 From: Stan Wiechers <150920+whoisstan@users.noreply.github.com> Date: Wed, 15 Apr 2026 09:27:51 -0400 Subject: [PATCH] --gc-interval is allocation based and not time based node --v8-options ... --gc-interval (garbage collect after allocations) type: int default: --gc-interval=-1 Signed-off-by: Stan Wiechers <150920+whoisstan@users.noreply.github.com> --- pages/diagnostics/memory/understanding-and-tuning-memory.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/diagnostics/memory/understanding-and-tuning-memory.md b/pages/diagnostics/memory/understanding-and-tuning-memory.md index fb0f128..3e45ecd 100644 --- a/pages/diagnostics/memory/understanding-and-tuning-memory.md +++ b/pages/diagnostics/memory/understanding-and-tuning-memory.md @@ -124,7 +124,7 @@ For example, in a real-time application like a stock trading platform, you may w node --gc-interval=100 app.js ``` -This setting forces V8 to attempt garbage collection every 100 ms. You may need to adjust this interval for specific use cases, but be cautious: setting the interval too low can cause performance degradation due to excessive garbage collection cycles. +This setting forces V8 to attempt garbage collection every 100 allocations. You may need to adjust this interval for specific use cases, but be cautious: setting the interval too low can cause performance degradation due to excessive garbage collection cycles. ### `--expose-gc`