>>but they're only allowing<<
Notice on the list provided by `trailfox` the "≈ CPU Load" column -- when the programs are written to use 4 cores "they're" allowing Go to access 4 cores.
Re:Playing with Go1.1beta2, it's much faster
by carbocation on Wednesday April 10, 2013 @11:52AM
(#5525877)
No. Go programs currently require a one-line instruction to tell them how many cores to use. Without that one line, they will only use one core.
The go program in question was written without that instruction; therefore, it's only allowed to use one core.
Re:Playing with Go1.1beta2, it's much faster
by igouy on Wednesday April 10, 2013 @12:47PM
(#5526310)
>only allowed to use one core<
Only "allowed" by who?
If you mean that "the Go program in question" is by-design a sequential program then -- yes of course it is!
The contributed Go programs that were written for multi-core use more than one core -- http://benchmarksgame.alioth.debian.org/u32q/program.php?tes...
http://benchmarksgame.alioth.debian.org/u32q/program.php?tes...
Note that:
1) It only ever uses one core, because
2) It isn't configured with GOMAXPROCS, which therefore defaults to 1.
So, sure, they have an N-core machine, but they're only allowing go to access 1 core.