I will still say that it would not take long to bottleneck 20Gbps connection dependent on usage purposes. imagine every WOW player downloading the latest 20GB update all at once. They all max there connection 1Gbps the server then faces an issue of having enough bandwidth this is where limits come into play so that the server can provide that latest update to every user downloading it while giving every user 1Gbps. Being able to limit the connection is kinda different. there is how many internet connected people? even if just half of them were using that shiny 1Gbps connection the net would start to feel the effects. 20Gbps really is not much when you start putting load onto that connection. Current infrastructures can support faster then what most people have. So why do we not have faster speeds? The "world wide web" would hurt.
I may be wrong however this is based on my understanding of networking and understanding of the bigger world wide web (computer talks to computer that talks to computer)
This is a good point. Given enough connections, a server can be overloaded.
This is why we have massive data centers and cloud computing now.
For a small company, with only a single server, they would certainly run into trouble. I would argue that other resources on the server would fail before a bandwidth issue though. In most cases, I see that RAM limits the number of connections. So your bottleneck is going to be your slowest or smallest resource.
Another thing to consider. If many people are downloading that 20GB file, the ones with faster connections are going to finish the download faster. So once the download is done, they leave the queue and are eliminated from the bottleneck.
940 down / 880 up and around 8ms ping.
200mbps down and 20mbps up
5MBps /1MBps lol
90 MBps / 90 MBps![]()
/.\ lllolll ..i..
Last edited by splikcit; 02-11-2019 at 04:17 AM. Reason: lol
I think 12 MBps / 1 MBps
56kb/s dial-up