Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/dist: ~1GB memory needed for testing, problems on arm (Raspberry Pi 2) #14144

myannikos opened this issue Jan 29, 2016 · 2 comments


Copy link

@myannikos myannikos commented Jan 29, 2016

go version devel +6d61725 Thu Jan 28 21:10:22 2016 +0000 linux/arm

Linux raspberrypi 4.1.13-v7+ #826 SMP PREEMPT Fri Nov 13 20:19:03 GMT 2015 armv7l GNU/Linux
(default Raspian Jessie, updated)

When compiling and testing (all.bash) this Go version with itself, the 4 core / 1GB Pi 2 almost chokes (>90% iowait, takes a long time).

This seems unnecessary, as it is due to parallelism when running "go tool dist test..." especially in the go/test directory. I am seeing 14 x "go", 4 x "compile" and 4 x "runtest.exe" processes executing at the same time.

GOMAXPROCS setting seems to have no effect due to the code in cmd/dist/util.go, which sets maxbg to at least 4 even on low memory 4 core systems like the Pi 2. It seems that builds could run much more smoothly with even 512MB if GOMAXPROCS was honored there.

@bradfitz bradfitz added this to the Go1.7 milestone Jan 29, 2016
@ianlancetaylor ianlancetaylor changed the title ~1GB memory needed for testing, problems on arm (Raspberry Pi 2) cmd/dist: ~1GB memory needed for testing, problems on arm (Raspberry Pi 2) May 16, 2016
Copy link

@bradfitz bradfitz commented May 19, 2016

Timeout. Moving to Go 1.8, unless @davecheney has an easy fix.

@bradfitz bradfitz modified the milestones: Go1.8, Go1.7 May 19, 2016
Copy link

@myannikos myannikos commented May 20, 2016

No memory shortage issues on Pi2 with all.bash building +b3bf2e7 (about ~150M left of 1GB). Closing issue, thanks.

@myannikos myannikos closed this May 20, 2016
@golang golang locked and limited conversation to collaborators May 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.