The quiet plan to make the internet feel faster
-
CEOs everywhere: "So we can fill that bandwidth with more ads!"
Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver
-
It is not the internet that is slow, it is the damned webs that make it slow. Back to how it should be | CommitStrip[^]
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
The Verge[^] wrote:
A few months ago, I downgraded my internet, going from a 900Mbps plan to a 200Mbps one. Now, I find that websites can sometimes take a painfully long time to load
There you lost me. Sorry, that just doesn't hold water. I believe that sometimes, website can take long to load - but that is most certainly not because your subscriber line is "just"
-
Quote:
The Verge[^] wrote: A few months ago, I downgraded my internet, going from a 900Mbps plan to a 200Mbps one. Now, I find that websites can sometimes take a painfully long time to load
There you lost me. Sorry, that just doesn't hold water. I believe that sometimes, website can take long to load - but that is most certainly not because your subscriber line is "just" 200 Mbps. I would guess that "painfully long" is at least a second, and your typical web page does not require 20 megabytes of HTML code. You should either open Resource Manager, the Network tab, and watch how often the dynamic Network wind hits a roof of 200 Mbps. My guess is that it never happens. Or, open Control Panel | Network Connections, and take note of the "Received"
-
Am I the only one remembering ATM? Not cash machines, but Asynchronous Transfer Mode. A physical level protocol designed for an end-to-end maximum latency of 300 ms. Globally. The first version of the standard, 35 years ago, specified 155 Mbps and 620 Mbps user interfaces; 2.4 Gbps and 10 Gbps was for internal network switches. Like a telephone connection, an ATM connection was routed end-to-end at the physical level. The physical level also handled statistical multiplexing for virtual connections. I have heard (no URL available) that there were IP routing networks using virtual ATM connections for single-hop routing between any two routers connected to the ATM network, significantly reducing latency and processing overhead. But ATM fell as a victim to the Network Wars. I never saw any good technical reasons why ATM should fail - but a lot of network-political reasons. I really wouldn't object to an ATM revival ... (Alternately: If someone would provide really good technical arguments why ATM deserved to fail, I'd like to learn about it. But I strongly doubt that there are many people around today that know ATM well enough to really give it a critical assessment, and certainly not without being colored by the Network Wars.)