automaxprocs
lxcfs
automaxprocs | lxcfs | |
---|---|---|
6 | 1 | |
3,788 | 998 | |
1.7% | 1.1% | |
6.0 | 6.8 | |
3 months ago | 6 days ago | |
Go | C | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
automaxprocs
-
Go, Containers, and the Linux Scheduler
We use https://github.com/uber-go/automaxprocs after we joyfully discovered that Go assumed we had the entire cluster's cpu count on any particular pod. Made for some very strange performance characteristics in scheduling goroutines.
-
Senior engineer here trying to pick up Go for jobs. What resources can you recommend me to cover as much ground as possible
Follow notable issues on https://github.com/golang/go to understand such things like why https://github.com/uber-go/automaxprocs was created.
-
Setting GOMAXPROCS without CPU limits in Kubernetes?
Please never set the value manually in a kubernetes production environment. Use https://github.com/uber-go/automaxprocs
-
What are goroutines and how are they scheduled?
There is an environment variable (GOMAXPROCS) that you can set which determines how many threads your go program will use simultaneously. You can use this great library from Uber to automatically set the GOMAXPROCS variable to match a Linux container CPU quota. If you are running Go workloads in Kubernetes, you should use this.
-
Shouldn't have happened: A vulnerability postmortem
AFAIK, it hasn't changed, this exact situation with cgroups is still something I have to tell fellow developers about. Some of them have started using [automaxprocs] to automatically detect and set.
[automaxprocs]: https://github.com/uber-go/automaxprocs
-
CPU throttling despite being well below the limit
For you own applications, you can use: https://github.com/uber-go/automaxprocs
lxcfs
-
Go, Containers, and the Linux Scheduler
> I wondered for a while if docker could make a fake /proc/cpuinfo
This exists: https://github.com/lxc/lxcfs
lxcfs is a FUSE filesystem that mocks /proc by inferring cgroup values in a way that makes other applications and libraries work without having to care about whether it runs in a container (to the best of its ability - there are definitely caveats).
One such example is that /proc/uptime should reflect the uptime of the container, not the host; additionally /proc/cpuinfo reflects the number of CPUs as a combination of cpu.max and cpuset.cpus (whichever the lower bound is).
As others also mentioned, inferring the number of CPUs could also be done using the sched_getaffinity syscall - this doesn't depend on /proc/cpuinfo, so depending on the library you're using you might be in a pickle.
What are some alternatives?
rfcs - RFCs for changes to Rust
LXC - LXC - Linux Containers
go-perfbook - Thoughts on Go performance optimization
x11fs - A tool for manipulating X windows
go-licenses - A lightweight tool to report on the licenses used by a Go package and its dependencies. Highlight! Versioned external URL to licenses can be found at the same time.
GlusterFS - Gluster Filesystem : Build your distributed storage in minutes
sudo - Utility to execute a command as another user
go - The Go programming language
go-internals - A book about the internals of the Go programming language.
guide - The Uber Go Style Guide.
tiny-rust-executable - Using Rust to make a 137-byte static AMD64 Linux executable
go101 - An up-to-date (unofficial) knowledge base for Go programming self learning