Recently one of my apps went out of control and began uploading continuously as fast as it could, more or less saturating the up channel. I noticed to my surprise that this coincided with an extreme drop-off of my down channel, to the extent that I could barely browse and was even having to wait for DNS lookups to happen. This made my ADSL unusable for practical purposes, so I had to kill the rogue app and stop the uploading. Then downloading returned to normal.
Being over 4 km from the exchange, I get about 2.8 Mbps download at best; this sometimes drops off a lot, possibly due to contention. I get about 0.37 Mbps upload at best. But when uploading continuously, the download almost disappears - maybe 20 Kbps at best.
I had always believed that ADSL provided separate and independent channels for uploading and downloading, although with very different bandwidths. But my ISP says that "ADSL is asynchronous meaning they both share the same capacity, so higher upload usage reduces the download availability". That doesn't look right to me. For a start, I don't see what asynchrony has to do with it. And I read on Wikipedia (the source of all perfectly authoritative correct information!) that:
"Currently, most ADSL communication is full-duplex".
and
"A /full-duplex/, or sometimes /double-duplex/ system, allows communication in both directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line telephone networks are full-duplex, since they allow both callers to speak and be heard at the same time. A good analogy for a /full-duplex/ system would be a two-lane road with one lane for each direction".
The only weak link there is the "most" in the first quote. Is British (BT) ADSL an exception, in that the up and down channels share bandwidth? Or is it just that when the up channel gets saturated, the necessary acknowledgements etc. are slowed down?
Lastly, is there any reasonable workaround?



Print Thread
TomWelsh