mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2026-06-29 21:46:01 +03:00
79c08ecac4
Historically some of VictoriaMetrics components were optimized for the low rate of memory allocations. These are: vmagent, single-node VictoriaMetrics and vmstorage. These components benefit from the low GOGC value, since this allow reducing their memory usage in steady state on typical workloads. Other VictoriaMetrics components aren't optimized for the reduced rate of memory allocations. This results in the increased CPU usage spent on garbage collection (GC) in these components, since it must be triggered at higher rate. See https://tip.golang.org/doc/gc-guide#GOGC for details. These components do not use too much memory, so it is OK increasing the GOGC for these components from 30 to 100 - this won't affect the most users. Keep GOGC to 30 only for vmagent, single-node VictoriaMetrics and vmstorage components. See077193d87cand54b9e1d3cb. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7902
See vmagent docs here.
vmagent docs can be edited at docs/vmagent.md.