-
Notifications
You must be signed in to change notification settings - Fork 17.6k
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
building | testing go parallelly. #39463
Comments
It is already done in parallel, as controlled by the (If you are aware of areas where it could usefully be more parallel, please let us know.) |
Thanks a lot for pointing this out. What's real value for this variable? Is it set automatically according to the number of physical cores on user's machine? |
I defaults to GOMAXPROCS |
|
@ianlancetaylor Do you mean it will account into the hyper threading results? |
Whatever your operating system counts as a core is what go build will use. |
Do you mean the following counting method:
|
The method differs by operating system and processor. Stepping back for a moment, what is the problem you are having? You've mentioned something about building Go code in parallel. To the best of my understanding the Go tool builds packages in parallel by running multiple copies of the go compiler -- one per package, up to GOMAXPROCS by default or |
@davecheney I compile go git master version on a dual Xeon E5-2699v4 (44 physical cores in total) machine with 256 G ram. It takes several minutes for buildings and testings. So I want to know whether this is reasonable. |
I think a few minutes is a reasonable time to execute |
Hi,
When I compile go from source code with the following two methods:
Is it possible for me to do the job parallelly, i.e., like the manner of
make -j N
?Regards,
HY
The text was updated successfully, but these errors were encountered: