Power9 has 120MB of L3 cache that's shared between all cores. Which means you can ACTUALLY have a full 120MB-sized problem set and share all that information between cores.
In short: Threadripper is great for sure, but its not necessarily a fair comparison. In an apples-to-apples comparison (ie: Monero Mining), it seems like a Power9 server is 3x better than Threadripper (Power9 gets ~3000 hash/sec, while Threadripper is roughly 1000 hash/sec).
https://www.phoronix.com/scan.php?page=news_item&px=POWER9-C...
> Using the xmr-stak-power PPC64LE-focused Monero miner, they are seeing great performance with it running on dual pre-production 16-core POWER9 processors. There's a hash rate of 2945H/s while this POWER9 system is pulling 350 Watts DC power.
And mind you: Monero / Cryptonight only uses 2MB of L3 per core. So that's practically Threadripper's ideal problem. Imagine if you actually had a dataset that was larger than the 8MB per CCX that Threadripper is limited to.
Not to hate on Threadripper at all. Its cheap and high performance. I'm seriously considering a Threadripper system myself. But these Power9 specs are incredible, and I'd definitely like to test one if I could afford one.
https://www.youtube.com/watch?time_continue=226&v=CS7M392Ia_...
I'm sure there are workloads that really do benefit from the huge unified L3, but it seems like a pretty small niche.
Each Power9 is consisting of either 2-super slices or 4-super slices, depending on which Power9 you get. (Corresponding to 4x SMT or 8x SMT respectively).
Threadripper has 4x integer pipelines, 4x floating point pipelines, and 2x load/store units (called AGUs by AMD) and supports 2-threads (aka: 2x SMT).
So Threadripper definitely is "broad", but Power9 is "broader". The 8x SMT Power9 can perform 8x loads / stores per cycle per core, while AMD's Threadripper can only perform 2x loads/stores per cycle per core.
IBM has extremely flexible hardware which, using IBM's hypervisor, can be configured on the fly to present itself in a number of different ways. For example: few powerful compute units, many medium compute units, or very many less capable compute units.
So right up front the idea (which a lot of people might assume without really thinking about) that a given chip has a fixed number of "cores" doesn't really hold true. More to the point the next question that presents itself "what makes up for a core and what determines how many a given processor has" is best answered with "it depends" (at least as far as IBM Power goes).
One of the main reasons this matters is that all sorts of businesses use the idea of "cores" as a fixed entity as part of their pricing structures... and now it's all muddied.
In regards to cores, the distinction is between the PowerVM and Linux (OpenPOWER/PowerNV) ecosystem variants. Both are made to process 96 threads, but the difference is in whether the thread processing units are grouped eight to a core (SMT8) or four to a core (SMT4).
The PowerVM version, some say for licensing reasons, gets the SMT8 cores. Either way, you get 96 threads:
12 cores * SMT8 = 96 threads 24 cores * SMT4 = 96 threads