You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v24.1, we made the following change: cockroachdb/cockroach#119605. This PR sets a default value for the GOGC of 300, which will allow the Go memory to quadruple before each garbage collection. The old default was to GC each time the memory doubled.
This will look like an increase in "Memory usage" in the Hardware dashboard and an increase in "Go total memory usage" in the Runtime dashboard. This should not cause OOMs, as the Go memory limit (controlled by --max-go-memory flag) will still prevent Go memory from growing too large. Still, it may be concerning to users who are not expecting it (like it was in this thread), so we should call it out in the release notes.
Nathan VanBenschoten (nvanbenschoten) commented:
In v24.1, we made the following change: cockroachdb/cockroach#119605. This PR sets a default value for the GOGC of 300, which will allow the Go memory to quadruple before each garbage collection. The old default was to GC each time the memory doubled.
This will look like an increase in "Memory usage" in the Hardware dashboard and an increase in "Go total memory usage" in the Runtime dashboard. This should not cause OOMs, as the Go memory limit (controlled by
--max-go-memory
flag) will still prevent Go memory from growing too large. Still, it may be concerning to users who are not expecting it (like it was in this thread), so we should call it out in the release notes.Jira Issue: DOC-10266
The text was updated successfully, but these errors were encountered: