5 ms·
Ask HN: HTTP on Bare Metal?
Both for research purposes and fun, I'm trying to see how fast I can make a single HTTP request.
Although I realize I can't control most factors (network latency, distance from the data center, speed of the responding API, etc) I want the machine to...
1. Send an HTTP request.
2. Save the response
... as fast as possible when it comes to the factors I can control. I only need to do it once and there's no need for scaling or production issues for consistency / reliability.
I realize this is a hopelessly neophyte question for all the high frequency people out there, but interested in getting started understanding these elements of the stack.
- sharemywin 10y agoC or Assembly? what OS? Are you talking about writing to the TCP/IP network layer or rewriting it at like an ethernet firmware layer?
- CoreSet 10y agoGood question! I'm assuming the OS would be a stripped down version of Debian or maybe a server-based, CL-only version of another Linux distro like Ubuntu. Although you can tell I'm fumbling here, I think the question I'm asking related more to the TCP/IP network layer. How can I construct a simple HTTP request at that level while adding the least overhead via the language/tools I'm using? What would rewriting the ethernet firmware look like?