cmd/dist: feature request: control over maximum number of CPUs used during build and test #22445
Comments
As far as I know the build part will honor Since what matters is basically the default value of |
I just tried a run with
from: https://golang.org/pkg/runtime/ . Also, my attempts to find info on Max OS X cpu affinity reveals this, though it may be dated by now. |
Maybe |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version
go version devel +a31e0a4aac Sat Oct 21 11:32:53 2017 +0000 darwin/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/sean/go"
GORACE=""
GOROOT="/Users/sean/goLang/go"
GOTOOLDIR="/Users/sean/goLang/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/75/tsmllrjr8xl81b0059bfyyd00000gs/T/go-build923680158=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
What did you do?
Invoke
all.bash
after updating withgit fetch
andgit pull
.What did you expect to see?
No more than
$GOMAXPROCS
used during the build and testing process.What did you see instead?
Every processor available being utilized.
I really like to be able to limit the number of logical processors that the build and test process Go uses. The logical choice would be for the process to respect the environment variable
GOMAXPROCS
. The reason for wanting to impose this limit is to manage the amount of heat produced on my system during the process.The text was updated successfully, but these errors were encountered: