Hacker News Reader

Comment by zasdffaa | Hacker News Reader

I'm interested, what are you doing that can eat all those cores>

Anyone working on even a medium sized C++ project needs a very high end machine in order to compile. For large projects, 32 core work stations aren't crazy at all. Try building something like Firefox or Chromium on a quad core and you will see what I mean. The cost of the workstation is tiny compared to the cost of the engineer and you really don't want them to be waiting around for half their day (quite literally) because of a miserly equipment budget.

I talked about linux recompiles because sometimes you do need the cores; not arguing. But that's the long tail and many devs don't. I'm not against blowing cash if needed, but really it's about asking if there are more efficient ways. I guess we agree.

Compilation is largely memory bandwidth limited - some of the acceleration from cores might be that they have different memory channels rather than more CPUs.

M1 builds a lot faster than Intel CPUs even with fewer cores because of the memory bandwidth.

Really?? I am very surprised, do you have any pointers on this? Kind of important thing to me, thanks.

It's pretty easy to eat up cores when you're developing graphics rendering algorithms, which can be far more convenient and ergonomic to do on the CPU in a general purpose compiled language, and scaling out via plain old threads.

A CPU with so many general purpose high-perf cores that it manages to look like a GPU in terms of execution units count is a beautiful thing.

Reply on news.ycombinator.com