Yup, i did say you got me confused, for some reason the moment i read 'die' my brain thinks of the old northbridge/southbridge way of doing things and CPU's being not much more than cores.
Would you have a link to any pics, I've read they used custom made motherboards with 32-phase power system and used a seriously powerful refrigerant system to chill the water down to 4°C, but i can't find any pictures.
Last edited by Corky34; 06-06-2018 at 06:42 PM. Reason: Asking for pics
Found some pictures of the cooling intel used, cant believe intel tried to make it out as if this was a real world scenario!
Look at the cooling on the VRMs its insane! I believe its also a non standard board so again would be another cost where as threadripper works in the current x399 without issue and can be air cooled sufficiently.
The cooler has a cooling capacity of 1650w as well... madness.
I wasnt expecting AMD to delivery double the cores on threadripper but its certainly a good item from the sounds of it, impressed how good their marketing and product releases have been now that they have solid products to sell. Looks like the future is pretty bright for AMD finally!
Corky34 (07-06-2018)
Some details leaked about 7NM Epyc:
https://www.servethehome.com/amd-epy...ds-per-socket/
64 cores!!
I saw this linked on AT forums:
https://www.youtube.com/watch?v=Kr8ZekIZUWI
Apparently that is the cooler AMD used for its Threadripper 2 systems.Its called the Coolermaster AMD Ryzen Wraith Ripper cooler.
If the link is true,that means 8 cores per CCX,meaning Ryzen 3 CPUs are 16 cores and the APUs will be 8 cores! If the latency clockspeeds have improved,a Ryzen 3 3300X might do the job for me!!
This is the cooler AMD used for its TR2 systems:
https://i.imgur.com/qkjksei.jpg
Doing the 28 core at 5GHz is an amazing feat nonetheless but it was horrifically misleading to make people think it was going to be a commercially available part within a reasonable scope of time. It feels like they were just trying to "one up" using a cannibalised Xeon.
32 core threadripper though, i wonder if it's epyc under the hood and i wonder what the actual clocks will be. But the fact they've got a 32 core part in the same socket is pretty damn fabulous. Really curious to see how far this part goes.
The core and frequency war just took a big step...
That Intel shizzle cracked me up, tells you a lot about their head space currently.
It might still make sense to keep a CCX with 4 cores, and double the CCX count. That would allow a "low end" part with just 4 cores on a tiny die. But really it's down to whether more cores in the CCX makes it too hard to keep the cache latency good hurting performance.
Big caches are slower than small caches, else we would just get one massive L1 cache. That's one of the reasons I wonder if AMD will just add more CCX modules at 7nm, twice the CCX modules means twice the cache as well as twice the cores, the only possible performance hit then is on scaling the infinity fabric to cope with the extra ports.
I can't see them increasing the CCX core count as it would require a pretty radical redesign, adding more CCX's to a package shouldn't increase the latency beyond the baseline increase of going from CCX to CCX, infinity fabric can transfer directly node-to-node, island-hopping in a bus topology, or as a mesh topology system so beyond the delay in the electrical signal you shouldn't see a difference in latency from going to a neighboring CCX or one in the opposite corner (in a grid of 2x3, 3x3, 4x4).
They wouldn't really need to do a grad anyway, since going 2x2 would give them the 16 core count and make it "relatively" easy to directly connect all the CCXes to each other. 4 way communication will be more complex and slightly slower than 2 way, but I suspect they'll be able to mask that reasonably well - EPYC doesn't seem to suffer too much from 4 way communication between dies in an MCM, which should be a magnitude more problematic than between complexes on the same die.
Interesting times ahead, whatever they choose to do...
There are currently 1 users browsing this thread. (0 members and 1 guests)