3 ms·
Virtualization. Remember that these EPYC systems will have up to 64 cores per chip. 128 cores / 256 threads per 2P platform, with 128x to 160x PCIe 4.0 lanes d
by dragontamer 8y ago
Virtualization.
Remember that these EPYC systems will have up to 64 cores per chip. 128 cores / 256 threads per 2P platform, with 128x to 160x PCIe 4.0 lanes depending on the motherboard.
Lets say you split up your system into 32 VMs (4-cores / 8-threads per VM). That's only 4x to 6x PCIe 4.0 lanes per VM. Doesn't seem very spacious anymore, does it? That's barely enough room for a NVMe drive per VM + a small, shared chunk of graphics (modern enterprise GPUs can be virtualized and split between VMs. So one x16 link to a beefy GPU can be shared between 8 VMs)
If your current customer is using NVMe drives + thick-client workstations for docker / testing / etc. etc, it may be difficult to convince them to switch to a virtualized infrastructure. But a beefy machine with this much I/O would definitely catch their eyes.
- vel0city 8y agoThis, exactly. These chips are targeted for the heavy virtualization platforms (see: "The Cloud"). It means you can fit more customers in the same space and power envelope before you start running into noisy neighbor issues.
- masklinn 8y ago> These chips are targeted for the heavy virtualization platforms (see: "The Cloud"). They're very nice for big fast storage: https://www.dell.com/en-us/work/shop/povw/poweredge-r7415 https://www.dell.com/en-us/work/shop/povw/poweredge-r7415 > Front Drive Bays: Up to 24 x 2.5” […] NVMe That's 96 PCIe lanes right there., and drives are bandwidth-limited by 3x4. Especially if you want to plug that into a fast network, you need 3x16 per 100Gb port, or half a 4x16.