0
1
I've been having network problems for a while and I'm trying to track down the source of the issue.
Yesterday, I was transferring a file from my laptop to my desktop with SCP, over my wifi connection. I when the download started, both computers had low ping to the local router (192.168.1.1, both sat around 10ms-50ms) and the download ran at 2-3 MB/s.
After a minute or so, I found that my desktop's latency to 192.168.1.1 shot up dramatically (> 1,000 ms) and the transfer slowed to a crawl (~200 KB/s). The laptop's latency to 192.168.1.1 stayed the same, however (10-50ms). Once the transfer finished, the desktop's latency dropped back down to its normal range.
Clearly, something goes wrong when the connection is saturated. What could it be? Does this suggest a problem with the router, or a problem with my desktop? Where would be the right place to start looking?
Ummm... if a connection is saturated, then it is performing at its maximum capacity. By definition adding further traffic is going to cause packets to be queued and cause latency. – cpt_fink – 2015-04-17T04:40:33.220
@cpt_fink The transfer rate drops to 200 KB/s and stays there, which definitely isn't enough to kill the router. This is also over Wifi across my local network -- I would have hoped that I could max out at least 54 Mb/s. Also, latency stayed low on one computer but not the other --- wouldn't what you're describing cause a network-wide slowdown? – Patrick Collins – 2015-04-17T16:53:45.610