Packet Loss vs Latency

https://www.thetechfirm.com

I get involved with a lot of performance related troubleshooting and the majority of the time the root cause is related to packet loss or excessive latency.
Let me start with explaining the difference between the two terms. Packet Loss is literally when you do not receive a packet. This can be caused by a variety of reasons such as corrupted frames, RF interference, half full duplex mismatches, dirty fibre connectors, oversubscribed links and routing issues. Packet loss is an issue since TCP based protocols will have to wait and retransmit lost frames. The key word here is ‘wait’ since waiting implies you are no longer transmitting. For example, if you had a 500ms delay on 10 Mb link, you lost the opportunity to transmit 5 Mb within that 500 ms time frame. If your application is UDP based, all bets are off and it is up the application to decide what to do. I’ve seen UDP based applications react to packet loss by terminating the connection, resend data or corrupt data. With VOIP you hear echo and distorted audio.

read the rest at
https://www.networkcomputing.com/networking/packet-loss-vs-latency-analyzing-impact/523143466

Тэги:

#packet_loss #latency #network_troubleshooting #wireshark #protocol_analysis #TCP #UDP #tony_fortunato #thetechfirm.com #the_Technology_firm #network_computing

Скачать видео