Add runtime memory protection settings to Nitro memory management docs#3155
Open
a-thomas-22 wants to merge 15 commits intomasterfrom
Open
Add runtime memory protection settings to Nitro memory management docs#3155a-thomas-22 wants to merge 15 commits intomasterfrom
a-thomas-22 wants to merge 15 commits intomasterfrom
Conversation
Document node.resource-mgmt.mem-free-limit (RPC throttling) and node.block-validator.memory-free-limit (validation pausing), including how cgroup-based memory checking works, metrics emitted, log lines, and guidance on choosing between the two settings.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Delete the "Choosing between the two settings" subsection and its table that compared node.resource-mgmt.mem-free-limit and node.block-validator.memory-free-limit. Cleans up the Nitro memory management docs by removing the redundant/outdated comparison.
…nLabs/arbitrum-docs into at/affectionate-mahavira
| | **glibc malloc arenas** | Per-thread arena overhead for CGO allocations | No | `MALLOC_ARENA_MAX` | | ||
|
|
||
| Only the Go heap is subject to Go's garbage collector and `GOMEMLIMIT`. The CGO and `mmap` allocations are invisible to Go's runtime. They don't appear in `runtime.MemStats` or standard Go memory profiles, but they still consume container memory and count toward your memory limit. | ||
| Only the Go heap is subject to Go's garbage collector and `GOMEMLIMIT`. The CGO and `mmap` allocations are invisible to Go's runtime. They don't appear in `runtime.MemStats` or standard Go memory profiles, but they still consume er memory and count toward your memory limit. |
Contributor
There was a problem hiding this comment.
is "consume er memory" correct?
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
3 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.
Summary
node.resource-mgmt.mem-free-limit(RPC throttling via HTTP 429) andnode.block-validator.memory-free-limit(validation pausing) as a new "Runtime memory protection" sectionRef: SREP-2531