They should let this author commit changes to the runtime package docs, because this explanation of GOMAXPROCS is much more clear than the official docs.<p>This article: "the number of CPUs (whatever your operating system considers to be a CPU) visible to the program at startup."<p>Official docs: "The number of logical CPUs on the local machine can be queried with NumCPU." and "NumCPU returns the number of logical CPUs usable by the current process."<p>The problem with the official docs is they don't mention that the value of NumCPU is locked in at startup and never changes.
Site's down for me.<p><a href="http://webcache.googleusercontent.com/search?q=cache:OXupz2ZeSOAJ:dave.cheney.net/2015/11/29/a-whirlwind-tour-of-gos-runtime-environment-variables&hl=en&gl=us&strip=1&vwsrc=0" rel="nofollow">http://webcache.googleusercontent.com/search?q=cache:OXupz2Z...</a>
There's also GO15VENDOREXPERIMENT in Go 1.5. It enables dependency vendoring with a vendor/ directory for each package.<p>More details here: <a href="https://golang.org/s/go15vendor" rel="nofollow">https://golang.org/s/go15vendor</a>.