3 ms·
Cool but I think the following are safe assumptions: Most packets are dropped "elsewhere". Most packets are dropped due to misconfiguration, route loss (often d
by contingencies 5y ago
Cool but I think the following are safe assumptions: Most packets are dropped "elsewhere". Most packets are dropped due to misconfiguration, route loss (often due to power loss, link change or link integrity issues), or firewalling. Well written applications tend to survive regardless. IPv6 is nominally better than IPv4 in terms of surviving link state changes.
Also: The recent trend of putting everything down web sockets is bad, as it effectively regresses to circuit-switched networking with undefined QoS guarantees / failure types and crap tooling. Hopefully we've already passed 'peak websocket'.
- toast0 5y ago> Most packets are dropped "elsewhere". This is probably true, but elsewhere packet loss is often diffuse. If you're looking into packet loss, it's likely because something is overloaded on your machine resulting in a burst of loss that affects user experience or your stats. Surviving is great, but eliminating bottlenecks you can control is better.
- jeffbee 5y agoI don't take the statement that packets are dropped elsewhere as obviously true. Your own box will drop due to queue discipline buffer sizes, NIC queue pruning, and a hundred other reasons.
- cbzbc 5y agoI suppose the question is to what extent these reasons are a factor - as opposed to incorrect hashes, bad formats, invalid values, invalid sequence numbers etc. I assume this is why ‘elsewhere’ was in quotes.