Preventing default GC setting from eating all node RAM #2187
Conversation
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
Having 400 as a default GC threshold makes lua anable to recover memory at all! Eating out every single byte on node cluster.
Author
|
400 breaking through the roof almost instanlty: |
Member
|
We have being doing stress testing with 500 participants in a meeting and 10k for visitors to come to these values. The current settings use more RAM but makes GC to run less frequent which in stress times uses less CPU. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Having 400 as a default GC threshold ( in combination with speed equal 250 as a second default ) makes lua anable to recover memory at all! Eating out every single byte on node cluster: