Hacker News new | ask | show | jobs
by blibble 1223 days ago
> So even if you have a massive amount of cores in that machine, you still don't really have much time to spend on a single request and a single mutex operation will exceed your budget.

fortunately it's no longer 2000 and I have more than one core, and my NIC has more than one queue

generating requests is a lot less CPU intensive than parsing requests

how much CPU do I have to spend to get a pre-formed 100 byte request into the NICs queue? not much at all

(the TCP negotiation will likely be the bottleneck)

3 comments

Could you do this and write it up? I'd love to see how you tune this stuff in hardware and software to get that sort of throughput.
These were HTTP/2 requests, not connections, so no per-request TCP negotiation. I'd say it's very easy to generate a huge number of requests like this, even if it's over TLS.
I've interpreted the "put out" in the initial comment as in "put out a fire" (i.e. mitigate), instead of "send out".