3 ms·
Very cool post. Thank you. This article, and its many links, are helping noob me learn how to ask about I/O perf. TechEmpower benchmarks HTTP servers. While c
by specialist 5y ago
Very cool post. Thank you.
This article, and its many links, are helping noob me learn how to ask about I/O perf.
TechEmpower benchmarks HTTP servers. While contestants continue to improve, I've long been curious what the theoretical fastest HTTP server could be. https://www.techempower.com/benchmarks/ https://www.techempower.com/benchmarks/
Basically, an update to the "C10K problem" for the year 2021. https://en.wikipedia.org/wiki/C10k_problem https://en.wikipedia.org/wiki/C10k_problem
A bit like how Daniel Lemire initially thought about parsing JSON. Paraphrasing: Why can't a JSON parser run at wire speed? "Parsing JSON quickly: early comparisons in the wild"
https://lemire.me/blog/2019/03/02/parsing-json-quickly-early-comparisons-in-the-wild/ https://lemire.me/blog/2019/03/02/parsing-json-quickly-early...
--
Also, I really appreciate including the sound and cooling considerations. It's just great seeing the process of system design accommodating (balancing) multiple goals. Bravo.
- goodpoint 5y ago> Basically, an update to the "C10K problem" for the year 2021. https://en.wikipedia.org/wiki/C10k_problem https://en.wikipedia.org/wiki/C10k_problem No, routing, natting and terminating connections are very different problems. Especially if we consider different implementations.