The Go compiler does use parallelism internally, though it's not as simple 
as "if you have more cores it goes faster", since there has to be a balance 
given the Go toolchain will invoke the compiler concurrently on multiple 
packages too.

Related:

- https://github.com/golang/go/issues/48497
- https://github.com/golang/go/issues/73044

And probably other issues I have not read that describe things...
On Tuesday, December 16, 2025 at 6:39:45 PM UTC-8 Robert Engels wrote:

> 
> You can test this yourself easily. Just use cpuctrl or cpu sets - you 
> don’t need to reboot. I think Go compiles using Go so you can probably just 
> set max procs. https://go.dev/blog/container-aware-gomaxprocs
>
> On Dec 16, 2025, at 8:11 PM, '[email protected]' via golang-nuts <
> [email protected]> wrote:
>
> 
>
> How much faster does the go compiler run when presented with additional 
> cores?
>
> For example, let's say you boot Linux telling it you have just one 
> processor. You build the Go compiler.
>
> You then repeat this process for a number of times equal to the number of 
> processors you have in your system, each time increasing the number of 
> processors you tell Linux to use by one. How is the speed of compilation 
> affected by the number of processors? Is there a point when adding more 
> processors does no good?
>
> Cordially,
> Jon Forrest
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion visit 
> https://groups.google.com/d/msgid/golang-nuts/123fcf04-b6ee-4b34-bc4f-e7dc46947672n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/golang-nuts/123fcf04-b6ee-4b34-bc4f-e7dc46947672n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/golang-nuts/370c2c93-dfc8-4f3f-b852-e83dd66adf3cn%40googlegroups.com.

Reply via email to