4 ms·

>with 5% packet loss This is absolutely massive

• crazygringo 2y ago
  Clearly you have never taken the subway, or stood on a particular street corner with bad reception. Quite frequently I'd love to have just 5% packet loss.
• llm_nerd 2y ago
  It is bad packet loss, but is the sort of situations that people often find themselves in. Congestion, bad connections (which is a lot of mobile scenarios), satellite comms, and the like and it's a reality. It's interesting how people often say HTTP/3 only benefits the megas like Google. A few years back I worked on a data centric system (fund administration) where we had a single centralized server cluster serving high value users across the globe. Because of the integration and real-time nature of the data, it wasn't possible to replicate to servers around the world, nor was local (relative to the user) caching of much value at all. QUIC (which became HTTP/3) proved a significant improvement for users of the system. Users in the UK, Singapore, Australia, Germany, California, and so on, were all using a system in Toronto basically transparently, with great usability. That it was continents away suddenly didn't matter.
• aboardRat4 2y ago
  I live in a third world country, and here we consider 5% to be VERY good. Most if my servers have about 40-50% packet loss. 50% is just a half. So we naturally expect our 3000gbit links to turn into 1gbit links, but that's not how tcp works.