Gigabyte showcases their Aorus 15,000 MB/s PCIe 4.0 SSD

[WYP]

This is what PCIe 4.0 is capable of!



Read more about Gigabyte's Aorus 15GB/s NVMe SSD showcase.

 

[g0ggles1994]

Had to check this twice, thought the photo was a Navi reference card for a second

 

[NeverBackDown]

I wouldn't even know how to fill more than 2TB of that...

 

[ram8704]

So is this 4 2tb SSD's in raid 0 over PCIE4.0?

 

[NeverBackDown]

So is this 4 2tb SSD's in raid 0 over PCIE4.0?

Yes, it's the only way to reach 15,000MB/s with PCIe4.0 and 8TB of storage

 

[MiSJAH]

I wouldn't even know how to fill more than 2TB if that...

pr0n.

 

[MiSJAH]

Yes, it's the only way to reach 15,000MB/s with PCIe4.0 and 8TB of storage

What happened to the CPU DMI bottleneck?

 

[grec]

Infinity Fabric

 

[NeverBackDown]

What happened to the CPU DMI bottleneck?

That is for Intel.

This will only work for AMD at the moment until Intel can upgrade their DMI bandwidth. In normal terms people are more familiar with, upgrade from PCIe3.0 to 4.0.

 

[ram8704]

That is for Intel.

This will only work for AMD at the moment until Intel can upgrade their DMI bandwidth. In normal terms people are more familiar with, upgrade from PCIe3.0 to 4.0.

Man day by day the urge to switch to team red (AMD) grows.

 

[radus]

The last row is what really matters in 9/10 use cases. It's decent, but the newer Optane drives still beat it by roughly twice as much. Not many people would be able to fully utilize the sequential bandwidth. Using it for games would be a waste.

 

[grec]

Idk it's actually ridiculously rare you get truly random data request patterns in consumer workloads, and most of the ones you do get are very low intensity and unlikely to ever hit the limits, only common example that does is the pagefile really. Most software is still designed with the limitations of HDDs in mind so even though queue depths beyond 4 are still often avoided, the OS generally tries to make every queued command as close to sequential as possible. Even if you have a random data access pattern, as long as it isn't latency critical with an SSD you basically treat it as a sequential one, it's just branchy & latency critical software that forces constant no-queue depths.

For 90% of consumer use cases, loading OS', software, games, media, all the usual use cases you're basically just pulling big chunks of predictable data into RAM, or throwing big chunks of predictable data onto the drive(Installation or storage is rarely for low depth random access patterns unless you've got it set up as a scratch disk for some specific software).