mirror of
https://codeberg.org/superseriousbusiness/gotosocial.git
synced 2024-12-24 09:58:17 +03:00
acc333c40b
When GTS is running in a container runtime which has configured CPU or memory limits or under an init system that uses cgroups to impose CPU and memory limits the values the Go runtime sees for GOMAXPROCS and GOMEMLIMIT are still based on the host resources, not the cgroup. At least for the throttling middlewares which use GOMAXPROCS to configure their queue size, this can result in GTS running with values too big compared to the resources that will actuall be available to it. This introduces 2 dependencies which can pick up resource contraints from the current cgroup and tune the Go runtime accordingly. This should result in the different queues being appropriately sized and in general more predictable performance. These dependencies are a no-op on non-Linux systems or if running in a cgroup that doesn't set a limit on CPU or memory. The automatic tuning of GOMEMLIMIT can be disabled by either explicitly setting GOMEMLIMIT yourself or by setting AUTOMEMLIMIT=off. The automatic tuning of GOMAXPROCS can similarly be counteracted by setting GOMAXPROCS yourself.
17 lines
641 B
Go
17 lines
641 B
Go
package specs
|
|
|
|
// State holds information about the runtime state of the container.
|
|
type State struct {
|
|
// Version is the version of the specification that is supported.
|
|
Version string `json:"ociVersion"`
|
|
// ID is the container ID
|
|
ID string `json:"id"`
|
|
// Status is the runtime status of the container.
|
|
Status string `json:"status"`
|
|
// Pid is the process ID for the container process.
|
|
Pid int `json:"pid,omitempty"`
|
|
// Bundle is the path to the container's bundle directory.
|
|
Bundle string `json:"bundle"`
|
|
// Annotations are key values associated with the container.
|
|
Annotations map[string]string `json:"annotations,omitempty"`
|
|
}
|