> And Fastly shared the major improvements in time-to-first-byte they're seeing in the real world: What's time until last byte though? Yeah, The metric that g

> And Fastly shared the major improvements in time-to-first-byte they're seeing in the real world: What's time until last byte though? Yeah, The metric that got you promoted is cool and all, but if my application works on files atomically, it's the time until last byte that has meaning to me. I'm also gonna assume a bit more, and say it's also the byte where the service can start processing someone else's connection. So if http/3 increases the load on servers, with their CPU, instead of network hardware, with their ASIC, this would be a net loss as soon as you look at amount of complete requests per energy used. Instead of just looking at single session metrics. I guess I should probably read the HTTP/3 spec now...