Live data from Hacker News

AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

tomshardware.com

1–10 of 49 posts

Re: AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

#2
I wonder what's the good core count for development workstation. While it's obvious that increase from 4 cores to 12 cores is useful, for me it's not obvious that increase from 12 cores to 32 cores is similarly useful.

Sure, if I'm compiling huge project from the scratch, every core will be loaded, but that's more suitable for CI machine.

For everyday development people usually use incremental compilation and in my experience it's few files. So for me something like 12 cores looks like a golden balance between single core performance and multi core performance (because usually those high-core processors come with low frequency).

Re: AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

#3

I wonder what's the good core count for development workstation. While it's obvious that increase from 4 cores to 12 cores is useful, for me it's not obvious that increase from 12 cores to 32 cores is similarly useful. Sure, if I'm compiling huge project from the scratch, every core will be loaded, but that's more suitable for CI machine. For everyday development people usually use incremental compilation and in my e…

Test suite runs can take a long time. And sometime you touch that header which is, indirectly, included everywhere and trigger a global rebuild.

Still, a distributed build and test system would be superior anyway.

Re: AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

#4

I wonder what's the good core count for development workstation. While it's obvious that increase from 4 cores to 12 cores is useful, for me it's not obvious that increase from 12 cores to 32 cores is similarly useful. Sure, if I'm compiling huge project from the scratch, every core will be loaded, but that's more suitable for CI machine. For everyday development people usually use incremental compilation and in my e…

Multiple VM's and Thread ripper is used for content creation

Re: AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

#5

I wonder what's the good core count for development workstation. While it's obvious that increase from 4 cores to 12 cores is useful, for me it's not obvious that increase from 12 cores to 32 cores is similarly useful. Sure, if I'm compiling huge project from the scratch, every core will be loaded, but that's more suitable for CI machine. For everyday development people usually use incremental compilation and in my e…

A few years ago, when Intel had no competition, going for more than 6 cores meant that you had to sacrifice single-thread performance.

Now, if you want more than 8 cores, single-thread performance is not a reason to use less than 16 cores (AMD @ 4.7 GHz) or 18 cores (Intel @ 4.8 GHz).

You may want to use less cores for cost reasons, but not for performance reasons.

We do not know yet the frequencies for the 24-core Threadripper to be launched next month.

If they would succeed to have a 4.8 GHz single-core turbo, then ST performance would not be the reason to use less than 24 cores.

Re: AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

#6

I wonder what's the good core count for development workstation. While it's obvious that increase from 4 cores to 12 cores is useful, for me it's not obvious that increase from 12 cores to 32 cores is similarly useful. Sure, if I'm compiling huge project from the scratch, every core will be loaded, but that's more suitable for CI machine. For everyday development people usually use incremental compilation and in my e…

An example is when you are developing/testing distributed systems. Many tests which used to require a cluster to run can now be run on a single machine, which helps a lot with debugging.

Re: AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

#7

I wonder what's the good core count for development workstation. While it's obvious that increase from 4 cores to 12 cores is useful, for me it's not obvious that increase from 12 cores to 32 cores is similarly useful. Sure, if I'm compiling huge project from the scratch, every core will be loaded, but that's more suitable for CI machine. For everyday development people usually use incremental compilation and in my e…

My development environment has 12 discrete docker processes. The more cores the merrier!

Re: AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

#8

I wonder what's the good core count for development workstation. While it's obvious that increase from 4 cores to 12 cores is useful, for me it's not obvious that increase from 12 cores to 32 cores is similarly useful. Sure, if I'm compiling huge project from the scratch, every core will be loaded, but that's more suitable for CI machine. For everyday development people usually use incremental compilation and in my e…

My development environment has 12 discrete docker processes. The more cores the merrier!

I'd imagine more mem would likely be more helpful? Sure you're not thrashing? Sorry if I'm patronising you... but thrashing is a killer

Re: AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

#9

I wonder what's the good core count for development workstation. While it's obvious that increase from 4 cores to 12 cores is useful, for me it's not obvious that increase from 12 cores to 32 cores is similarly useful. Sure, if I'm compiling huge project from the scratch, every core will be loaded, but that's more suitable for CI machine. For everyday development people usually use incremental compilation and in my e…

And yet, GPUs have hundreds to thousands of cores, and we find them very useful...

There are many, many useful tasks which are embarassingly parallel or nearly so. For those tasks, doubling the core count doubles the performance. Single core gains have stagnated, so a performance doubling is a huge win. There's no other way to just up and double performance for any class of problem.

And even outside those tasks, more cores means more simultaneous heterogeneous workload, which means deeper and richer information pipelines. If you're live editing audio or video, for example, your core count determines the number of plugins/tracks you can work with simultaneously - and it's not unusual to have hundreds of tracks and dozens of layered plugins.

Re: AMD Lists Threadripper 3000 CPU with 32 Cores, Possible New Socket

#10
I'm curious about the 280 watt TDP, especially for the 16 core part. The 16 core Threadripper 2 had a 180 watt TDP, so what are they doing with the extra hundred watts on a smaller process? Could these chips be running at much higher frequencies?

We might really be at the brink of no-compromise super high end workstation computing!

Post reply on HN