3 ms·
For hyperscalers in the cloud and low latency finance, tcp is likely still king. You do not want things running on CPU as that is compute that could be sold to
by kd913 3y ago
For hyperscalers in the cloud and low latency finance, tcp is likely still king.
You do not want things running on CPU as that is compute that could be sold to someone else.
This needs an easy way to offload to a specialised hardware accelerator.
- jabart 3y agohttps://aws.amazon.com/blogs/aws/new-http-3-support-for-amazon-cloudfront/ https://aws.amazon.com/blogs/aws/new-http-3-support-for-amaz... Seems AWS is doing just fine with it. They also have built their own custom chipsets though I don't see a mention of it offloading QUIC to those chips.
- jeffbee 3y agoAWS in some ways wasn't really ready for something like QUIC to emerge. Nitro networking does, or did, penalize all UDP flows. Which obviously is not great for QUIC.
- belthesar 3y agoHyperscalers in the cloud and low latency finance will drive the innovation to make HW offload a thing sooner. For the rest of us normal folk, we can likely live with CPU managed packets until that happens, and then take advantage of the optimization benefits when they make it to us. I think it's fair to call this out, but my initial read, and the reason why I'm responding, is because it seems like you're saying that it's non-viable.