What is it?
Bandwidth saturation is a phenomena that occurs when all a circuits available bandwidth in a given direction is being utilized by a large upload or download; this results high latency and performance issues as subsequent packets start to buffer, eventually timing out and displaying symptoms such as slow speeds and packet loss.
Common Causes
Outside of simply uploading a large file via FTP or something like YouTube, commonly overlooked causes of bandwidth congestion are back-up software such as Dropbox or iCloud, seeding while torrenting, system updates (including mobile devices such as iPhones), large email attachments, and other similar circumstances.
Effects of Bandwidth Congestion on Latency
If you suspect upload saturation is occurring, the most direct method of identifying the source of the upload is to run a continuous ping test and remove devices from the network one at a time until ping responses go down to a reasonable level. Compare the following two ping test results:
Compare the following two ping tests:
$ ping 50.X.X.X PING 50.X.X.X (50.X.X.X) 56(84) bytes of data. 64 bytes from 50.X.X.X: icmp_seq=1 ttl=57 time=1135 ms 64 bytes from 50.X.X.X: icmp_seq=2 ttl=57 time=1106 ms 64 bytes from 50.X.X.X: icmp_seq=3 ttl=57 time=1161 ms 64 bytes from 50.X.X.X: icmp_seq=4 ttl=57 time=1115 ms 64 bytes from 50.X.X.X: icmp_seq=5 ttl=57 time=1096 ms 64 bytes from 50.X.X.X: icmp_seq=6 ttl=57 time=1108 ms 64 bytes from 50.X.X.X: icmp_seq=7 ttl=57 time=1144 ms 64 bytes from 50.X.X.X: icmp_seq=8 ttl=57 time=1131 ms --- 50.X.X.X ping statistics --- 10 packets transmitted, 8 received, 20% packet loss, time 9118ms |
Extremely high latency response times are one of the hallmarks of bandwidth congestion. Note that in addition to response times of over one second, that the above example is also losing packets due to time-outs.
$ ping 50.X.X.X PING 50.X.X.X (50.X.X.X) 56(84) bytes of data. 64 bytes from 50.X.X.X: icmp_seq=1 ttl=57 time=23.7 ms 64 bytes from 50.X.X.X: icmp_seq=2 ttl=57 time=23.4 ms 64 bytes from 50.X.X.X: icmp_seq=3 ttl=57 time=24.3 ms 64 bytes from 50.X.X.X: icmp_seq=4 ttl=57 time=63.1 ms 64 bytes from 50.X.X.X: icmp_seq=5 ttl=57 time=23.6 ms 64 bytes from 50.X.X.X: icmp_seq=6 ttl=57 time=22.9 ms 64 bytes from 50.X.X.X: icmp_seq=7 ttl=57 time=25.3 ms 64 bytes from 50.X.X.X: icmp_seq=8 ttl=57 time=25.9 ms 64 bytes from 50.X.X.X: icmp_seq=9 ttl=57 time=33.8 ms 64 bytes from 50.X.X.X: icmp_seq=10 ttl=57 time=23.3 ms --- 50.X.X.X ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9077ms |
In this second example, we see the same line after the upload has been stopped. Response times are back to normal, and we are no longer seeing packet loss.
Troubleshooting
File sharing program
File sharing programs are usually a fairly obvious generator of traffic on a DSL line. What people are sometimes unaware of is that some of these programs do not fully stop when you close the program. Some of these programs keep their shared folder open and continue to allow others to have access, using up bandwidth on the DSL line. If you use any file sharing programs, take a look through the icons in your task bar. You should find the culprit there if it is causing the issue.
Virus or Worm
Computers infected with internet worms can generate an incredible amount of traffic. A virus does not usually cause a huge amount of traffic on its own, but many spammers use email viruses to create a zombie spam relay, and nothing chokes a connection quite like a hundred thousand emails sent every minute.
Open wireless connection
An open wireless connection can be an invitation for unwanted guests. If you have an unsecured wireless router, or any wireless router, try enabling a password or disabling the unsecured network entirely and see how it affects the speed conditions on the line.
Useful Tools
Line Graphs
Sonic Fusion DSL customers can actually view their connectivity graphs via Member Tools -> Labs -> Fusion Line Profile -> View Graphs. As can be seen in the above example, this is what will show for periods where a line's upstream bandwidth is being intermittently saturated. In this instance, the circuit was hitting the maximum 1.2Mbps upload sync rate for extended periods of time, resulting in poor performance during these periods.
Network Resource Management Utilities
These resource management tools can also help diagnose if a specific program is the culprit behind upload saturation by checking Sent/Received Packets/Bytes.
The Windows Resource Monitor can be found by typing "perfmon /res" (no quotes) in Windows Search.
The Macintosh Activity Monitor is located in Applications > Utilities, or by searching in Finder for "Activity Monitor".
Further Reading:
- Network & DNS Troubleshooting Tools
- https://tools.ietf.org/html/rfc896
- https://en.wikipedia.org/wiki/Network_congestion
- https://en.wikipedia.org/wiki/Sliding_window_protocol
0 comments
Please sign in to leave a comment.