-
Notifications
You must be signed in to change notification settings - Fork 200
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.
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
feat: include memory limit in memory settings #1825
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -40,6 +40,13 @@ type CollectorsGroupMemorySettings struct { | |
// it will be embedded in the as a resource request of the form "memory: <value>Mi" | ||
MemoryRequestMiB int `json:"memoryRequestMiB"` | ||
|
||
// This option sets the limit on the memory usage of the collector. | ||
// since the memory limiter mechanism is heuristic, and operates on fixed intervals, | ||
// while it cannot fully prevent OOMs, it can help in reducing the chances of OOMs in edge cases. | ||
// the settings should prevent the collector from exceeding the memory request, | ||
// so one can set this to the same value as the memory request or higher to allow for some buffer for bursts. | ||
MemoryLimitMiB int `json:"memoryLimitMiB"` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do you think it is better to configure this as relative to the MemoryRequest field? (i/e with precentages or fractions relative to the request amount.) |
||
|
||
// this parameter sets the "limit_mib" parameter in the memory limiter configuration for the collector. | ||
// it is the hard limit after which a force garbage collection will be performed. | ||
// this value will end up comparing against the go runtime reported heap Alloc value. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we write the k8s value that will map into? and state that it will impact when the collector is OOMed?