3 ms·
Figure 3 (on the right) looks a lot like putting the memory controller back on the north bridge chip. And there’s reasons the memory controller was moved onto t
by rayiner 4y ago
Figure 3 (on the right) looks a lot like putting the memory controller back on the north bridge chip. And there’s reasons the memory controller was moved onto the CPU in the first place. Most workloads are very latency sensitive, with low latency ddr4 dimms outperforming much higher bandwidth ddr5 dimms.
- jeffbee 4y agoThe article is really about disaggregating memory from CPU capacity, and rightly points out that sometimes a marginal CPU in an SMP system is used purely as a memory controller.
- rbanffy 4y agoThe article mentions CTX is similar to IBM’s OMI, which they use in their high end POWER boxes. Their goal is to have separate processor and memory drawers on their servers to better mix and match workloads and capacity, trading latency for flexibility and bandwidth. I suspect their mainframes are next, as their RAM is located in the same drawer as the processors, but attached to a system controller chip (z15’s chip had almost a gigabyte of EDRAM working as an L4 cache on each drawer). With z16’s cache architecture, it may be better shielded from extra memory latency and able to work on a simpler NUMA topology.
- sliken 4y agoCXL isn't replacing system ram, it's just allowing you to have slow (compared to ram) connection to a big chunk of ram that's wicked fast (compared to storage). So you could for instance buy 16 nodes with 256GB ram then buy a couple 8TB connect CXL units. Then as needs dictate you could add any fraction of the CXL connected ram to any of those systems. Nobody is ditching CPU connected ram for CXL.