Sorry, but no - putting the burden on the developer to detect whether they are running in a container or not and then determine and adjust to cgroup settings is far too high an encumbrance on the service developer. This is a demonstrative example of a fundamental responsibility that should always be delegated to the runtime as the default behavior.
Neither Go 1.19 nor any subsequent version has "solved" this issue.
Neither Go 1.19 nor any subsequent version has "solved" this issue.