lotus/storage/sealer/cgroups.go

//go:build !linux
// +build !linux

package sealer

func cgroupV1Mem() (memoryMax, memoryUsed, swapMax, swapUsed uint64, err error) {
	return 0, 0, 0, 0, nil
}

func cgroupV2Mem() (memoryMax, memoryUsed, swapMax, swapUsed uint64, err error) {
	return 0, 0, 0, 0, nil
}
Use cgroup limits in worker memory calculations Worker processes may have memory limitations imposed by Systemd. But /proc/meminfo shows the entire system memory regardless of these limits. This results in the scheduler believing the worker has the entire system memory avaliable and the worker being allocated too many tasks. This change attempts to read cgroup memory limits for the worker process. It supports cgroups v1 and v2, and compares cgroup limits against the system memory and returns the most conservative values to prevent the worker from being allocated too many tasks and potentially triggering an OOM event. 2021-08-31 20:52:47 +00:00			`//go:build !linux`
			`// +build !linux`

storage: Move extern/sector-storage to storage/sealer 2022-06-14 18:03:38 +00:00			`package sealer`
Use cgroup limits in worker memory calculations Worker processes may have memory limitations imposed by Systemd. But /proc/meminfo shows the entire system memory regardless of these limits. This results in the scheduler believing the worker has the entire system memory avaliable and the worker being allocated too many tasks. This change attempts to read cgroup memory limits for the worker process. It supports cgroups v1 and v2, and compares cgroup limits against the system memory and returns the most conservative values to prevent the worker from being allocated too many tasks and potentially triggering an OOM event. 2021-08-31 20:52:47 +00:00
			`func cgroupV1Mem() (memoryMax, memoryUsed, swapMax, swapUsed uint64, err error) {`
			`return 0, 0, 0, 0, nil`
			`}`

			`func cgroupV2Mem() (memoryMax, memoryUsed, swapMax, swapUsed uint64, err error) {`
			`return 0, 0, 0, 0, nil`
			`}`