Skip to content

--gc-interval is allocation based and not time based #52

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
whoisstan wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

--gc-interval is allocation based and not time based #52

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/diagnostics/memory/understanding-and-tuning-memory.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Comment thread
avivkeller marked this conversation as resolved.

### `--expose-gc`

Expand Down