3 ms·
Throwing more cores at the problem isn't really terribly efficient, though. You don't see as much of a return as you might expect, especially when most things a
by freehunter 15y ago
Throwing more cores at the problem isn't really terribly efficient, though. You don't see as much of a return as you might expect, especially when most things aren't properly multithreaded.
- rwmj 15y agoOh sure, I understand it's not in Intel's interests at all. But it would sure make my builds faster if I could default to 'make -j16' (hyperthreads). I guess I'm not the target audience here.
- bunderbunder 15y agoI suppose it depends on the toolchain, but in my experience build time is mostly dominated by disk I/O nowadays. Even with my code stored on an SSD.
- SamReidHughes 15y agoWith C++ it is in my experience solidly CPU-bound, for example on 12 xeon cores, or 24 hyperthreading threads, and one 7200 RPM disk.
- freehunter 15y agoFor any compiling work I need to do, I usually offload to my Linode install with 4 Xeons. Your mileage may vary, though.