5 ms·
I’m shocked that a 256 core Epyc can’t do millions of requests per second at a minimum. Is it limited by the net connection or is there still this much ineffici
by api 9mo ago
I’m shocked that a 256 core Epyc can’t do millions of requests per second at a minimum. Is it limited by the net connection or is there still this much inefficiency?
- otterdude 9mo ago256 Processes x 10k clients (per the article) = 256K RPS
- mrweasel 9mo agoAren't you of by a zero? 10K requests per core / per second, time 256 cores is 2.560.000 RPS. There's probably going to be some overhead, but it seems like you could do 1M, if you have the bandwidth.
- cap11235 9mo agoI think the most likely bottleneck is gonna be your NIC hating getting a ton of packets. Line rate with huge frames is quite different than line rate with just ICMP packets, for instance (see CME binary glink market data for a similarly stressful experience to the ICMP).
- tempest_ 9mo agoLike anything it really depends on what they are doing, if you wanted to just open and close a connection you might run into bottle necks in other parts of the stack before the CPU tops out but the real point is that yea, a single machine is going to be enough.
- zipy124 9mo agoIt almost certainly can, even old intel systems with dual CPU 16 core systems could do 4 and a half million a second [1]. At a certain point network/kernel bottlenecks become apparent though, rather than being compute limited. [1]: https://www.amd.com/content/dam/amd/en/documents/products/ethernet-adapters/onload/onload-nginx-plus-benchmark-results.pdf https://www.amd.com/content/dam/amd/en/documents/products/et...