#Google drive download speed test software#

Your router's WAN port is Gigabit Ethernet.That is, let's say you have a situation like this: Short of that, if your router (possibly with aftermarket firmware) lets you do any kind of WAN port bandwidth limitation, you should limit what it sends out its WAN port to the effective upstream bandwidth of your broadband Internet connection. Look into bufferbloat and look at putting aftermarket firmware on your router that supports the anti-bufferbloat innovations that were pioneered in the CeroWrt project, such as FQ_CoDel (or plain CoDel) smart queueing and Explicit Congestion Notification (ECN).

#Google drive download speed test software#

However, poorly-designed router software that doesn't do smart queueing will be susceptible to a problem known as bufferbloat, which is where some poorly-designed routers focus too much on trying to never drop packets, so they buffer everything and let their buffer queues grow excessively long, which effectively hides the congestion from TCP (TCP uses dropped packets as a sign of congestion), preventing TCP from doing the congestion control that it's quite good at. If Google Drive uses TCP for its uploading, it shouldn't exacerbate congestion or cause increased latency, because TCP has built-in mechanisms for congestion avoidance and congestion control. If saturating your upstream causes high latency, it's a classic sign that you have a bufferbloat problem you need to fix. That said, on many home networks, saturating your upstream DOES cause high latency, but it is NOT just a fact of life you have to accept and live with, it's a bug that can be fixed, not just worked around by slowing down your uploads. You want uploads to saturate your upstream, otherwise you'd be wasting bandwidth and have needlessly prolonged uploads. Saturating your upstream SHOULD NOT cause high latency.