So what is the price for such a system
80M I/O Per Second with a Standard 2U System
21–30 of 41 posts
Re: 80M I/O Per Second with a Standard 2U System
#22Is this the death of kubernetes? Can I now use one server instead of 20?
Re: 80M I/O Per Second with a Standard 2U System
#23> The system has 2 CPUs with 64 PCIe Gen 4 lanes each, giving us plenty of PCIe lanes to connect NVMe SSDs Imagine if they used EPYC CPUs... 160 PCIe lanes.
They could have achieved this 'milestone', 1.5 yrs ago. Feels like an Intel ad to me.
Re: 80M I/O Per Second with a Standard 2U System
#24Is this the death of kubernetes? Can I now use one server instead of 20?
NVMe will allow your storage to be super fast, but it doesn't add any more compute resources. So unless your K8s cluster was all about IO, i'd say no...
Re: 80M I/O Per Second with a Standard 2U System
#25What is the point of that speed if the rest of your system is a bottle neck and the drives will fail in a year if you use that speed continously? I think we need to go back and look at cycles per bit (DWPD is confusing because you need to know the number of years and sometimes it's not mentioned on the product page). Complexity can increase some performance but there is always a cost to complexity. Optane seemed prom…
Re: 80M I/O Per Second with a Standard 2U System
#26What is the point of that speed if the rest of your system is a bottle neck and the drives will fail in a year if you use that speed continously? I think we need to go back and look at cycles per bit (DWPD is confusing because you need to know the number of years and sometimes it's not mentioned on the product page). Complexity can increase some performance but there is always a cost to complexity. Optane seemed prom…
>I think we need to go back and look at cycles per bit I've started playing around with new storage architectures for databases and with flash storage in mind. One thing I encountered that seems incredibly powerful, when combined with a log-based store, is micro batching of operations. When you aggregate a few hundred/thousand transactions together and then append them as modified subtrees to the end of a log, you st…
Direct I/O helps to avoid flushing the CPU cache through memcpy's to the kernel's page cache for a roughly 7% improvement, and io_uring helps to amortize the syscalls themselves into a single io_uring_enter() for a doubling of throughput for small 4 KiB read/write units, but having a first-class batching interface from end to end is the biggest win by far.
Re: 80M I/O Per Second with a Standard 2U System
#27Is this the death of kubernetes? Can I now use one server instead of 20?
Re: 80M I/O Per Second with a Standard 2U System
#28What is the point of that speed if the rest of your system is a bottle neck and the drives will fail in a year if you use that speed continously? I think we need to go back and look at cycles per bit (DWPD is confusing because you need to know the number of years and sometimes it's not mentioned on the product page). Complexity can increase some performance but there is always a cost to complexity. Optane seemed prom…
>I think we need to go back and look at cycles per bit (DWPD is confusing because you need to know the number of years and sometimes it's not mentioned on the product page).
This work is for people developing dedicated storage arrays, not your laptop. Datacenter optane is good for 60 DWPD. Given that it is most frequently used as a caching layer, it's extremely unlikely you'd exceed that in a well designed system.
https://www.intel.com/content/www/us/en/architecture-and-tec...
>Atleast SATA I can use in my laptops/desktops/consoles etc. Also nobody is looking at CPU usage of NVMe vs. SATA!
Literally every storage vendor in the market is looking at CPU usage of NVMe vs. SATA. There's a reason they benchmark in "a standard 2U system" and not a Dell Laptop or Desktop.
Re: 80M I/O Per Second with a Standard 2U System
#29Earlier quoted context omitted.
NVMe will allow your storage to be super fast, but it doesn't add any more compute resources. So unless your K8s cluster was all about IO, i'd say no...
I daydream about running our entire company k8s infra on a single 1U with 256 Epyc threads, a few terabytes of memory, and a bunch more of tiered storage. IMO this kind of miniaturization is amazing for container orchestration. Add a couple more, overprovision by 50%, let k8s handle the high availability, and you’ve got a datacenter in a small box.
Re: 80M I/O Per Second with a Standard 2U System
#30What is the point of that speed if the rest of your system is a bottle neck and the drives will fail in a year if you use that speed continously? I think we need to go back and look at cycles per bit (DWPD is confusing because you need to know the number of years and sometimes it's not mentioned on the product page). Complexity can increase some performance but there is always a cost to complexity. Optane seemed prom…
If you wanted simplicity you could have bought a single 2 TB drive.