3 ms·
AMD's design is clearly designed for cloud-servers with 4-cores / 8-threads per VM. Its so obvious: 4-cores per CCX sharing an L3 cache (that's inefficient to
by dragontamer 6y ago
AMD's design is clearly designed for cloud-servers with 4-cores / 8-threads per VM.
Its so obvious: 4-cores per CCX sharing an L3 cache (that's inefficient to communicate with other CCXes). Like, AMD EPYC is so, so so, SOOO very good at it. It ain't even funny.
Its like AMD started with the 4-core/8-thread VM problem, and then designed a chip around that workload. Oh, but it can't talk to the 5th core very efficiently?
No problem: VMs just don't really talk to other customer's cores that often anyway. So that's not really a disadvantage at all.
- dralley 6y agoIt's probably wrong to assume that that was their primary goal. The whole chiplet strategy makes an enormous amount of sense for so many other reasons that the one you suggest may well be the least important of them. Being able to use one single chip design as a building block for every single SKU across server and desktop has got to have enormous benefits in terms of streamlining design, time-to-market, yields, and overall cost. And then there's the financial benefits of manufacturing IO dies at Global Foundaries, and laying the groundwork for linking up CPU cores with GPU and FPGA chiplets directly on the package. It's a very flexible and economically sensible design that ticks a lot of boxes at once.