My bandwidth is ordinarily a few hundred kbps, but whenever I torrent it can reach up to 2 mbps, while all other traffic from me and my housemates is stuck in the single digit kbps range.

What does BitTorrent do so fucking well, and how can other protocols replicate this success? Would the total available bandwidth be different if every protocol did whatever enables BitTorrent to summon bandwidth from thin air?

One thing I know could be done is out-of-order fragments. TCP strictly orders the bytes because it doesn't know about messages, but an UDP-based message transfer protocol could just dump all parts of the message into the network at once and then wait for the recipient to ask for lost fragments. I know, we did this in a networking coursework.

... You're very likely to lose packets when you do this and so it sounds like less efficient use of the network, but since an ACK only has to be sent for many data packets, it's actually more efficient up to 50% packet loss. Additionally, this way the sender is at full liberty to strategize with the pacing of the packets based on known and observed network characteristics, so the protocol doesn't need to be changed to support a very high performance ceiling.

@lorentz I love how UDP sounds like absolute garbage, yet performs quite well.

@Root what's garbage about UDP?

@lorentz 😅

@Demolishun it's around 400 kbps and that because of really bad spatial layout. I'll route a cable through the kitchen of the new rental once I dealt with the mould. It's only in the single kbps range when there's a torrent download.

I have 100 mbps fiber paid for by my landlord, but I used to access the web using my Nokia 2700 as a USB modem.

Your housemate is seeding

UDP with zero flow control?