Aliaksandr Valialkin
|
c5770600a2
|
lib/cgroup: follow-up after b9bf3cbe3e
|
2021-02-08 15:54:38 +02:00 |
|
Nikolay
|
b9bf3cbe3e
|
refactored cgroups limits, (#1061)
adds tests, remove os.Exec
|
2021-02-08 15:46:22 +02:00 |
|
Aliaksandr Valialkin
|
4146fc4668
|
all: properly handle CPU limits set on the host system/container
This can reduce memory usage on systems with enabled CPU limits.
Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/946
|
2020-12-08 21:07:29 +02:00 |
|
Aliaksandr Valialkin
|
76b244cfcf
|
lib/cgroup: do not adjust the number of detected CPU cores via /sys/devices/system/cpu/online
The adjustement increases the resulting GOMAXPROC by 1, which looks confusing to users
as outlined at https://github.com/VictoriaMetrics/VictoriaMetrics/issues/685#issuecomment-698595309
|
2020-09-29 13:55:26 +03:00 |
|
Aliaksandr Valialkin
|
5c42965853
|
lib/cgroup: attempt to obtain available CPU cores via /sys/devices/system/cpu/online
See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/685#issuecomment-674423728
|
2020-09-22 23:27:19 +03:00 |
|
Aliaksandr Valialkin
|
f4c4ab811b
|
lib/cgroup: limit the maximum GOMAXPROCS value to the number of available CPU cores
There is no sense in setting GOMAXPROCS to value higher than the number of available CPU cores.
|
2020-08-28 09:49:32 +03:00 |
|
Aliaksandr Valialkin
|
ef7e2af8f5
|
app: respect CPU limits set via cgroups
Update GOMAXPROCS to limits set via cgroups. This should reduce CPU trashing and reduce memory usage
for cases when VictoriaMetrics components run in containers with CPU limits.
See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/685
|
2020-08-11 22:59:19 +03:00 |
|