You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2024/12/13 18:13:00 UTC
[jira] [Updated] (YUNIKORN-3000) Add support for setting GOGC / GOMEMLIMIT in Helm chart
[ https://issues.apache.org/jira/browse/YUNIKORN-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Condit updated YUNIKORN-3000:
-----------------------------------
Summary: Add support for setting GOGC / GOMEMLIMIT in Helm chart (was: Add support for setting GOMEMLIMIT in Helm chart)
> Add support for setting GOGC / GOMEMLIMIT in Helm chart
> -------------------------------------------------------
>
> Key: YUNIKORN-3000
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3000
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: release, release-notes
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
>
> As of Go 1.19, Go supports reading a {{GOMEMLIMIT}} environment variable to limit the amount of RAM the process will use before garbage collecting. This is a soft limit, but helps constrain resource usage and can help avoid being OOMKilled by Kubernetes. Since we set our existing memory request to 1 GiB, and limit to 2 GiB, I propose setting the default {{GOMEMLIMIT}} value to 1.5 GiB. This allows for non-GC overhead plus transient spikes, and should keep us well under the threshold for being OOMKilled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org