4 ms·

Right now the bottleneck is memory bandwidth & CPU lanes. NVMEoE lets you access storage from a VM that you can move around and, depending on what you are doing

Right now the bottleneck is memory bandwidth & CPU lanes. NVMEoE lets you access storage from a VM that you can move around and, depending on what you are doing, you are probably already serving traffic over your NIC. If you only need to do a minimal amount of I/O to disk all of the lanes used for I/O when you're idle is useless. If you are doing things like cache servers, DBs that manage replication for themselves, etc you can really optimize storage using this approach. Basically the difference between 25GB/s between your server and it's storage and 25GB/s between your server and it's clients is just where the packets are going.

rasz 5y ago
2x2.5GB/s for the whole system. Everything you can do with this you can do in classic system using cheaper COTS components. I simply dont see the point other than inventing new proprietary drives to cut off third party suppliers.
- paranoidrobot 5y ago
  > 2x2.5GB/s for the whole system. Pretty sure that's per drive.
  - deleted 5y ago
    [deleted]
- rektide 5y ago
  Its 2x25Gbps per drive. 25Gbe is quite cheap, not hard to do, low power & especially so over short backplanes. This chassis has 1.2Tbps switching, half for drives, half for attached computers. It's not proprietary. The drives can plug into ethernet. They speak industry standard NVMeoF; you could not get more standard if you tried.