Hacker News Reader

Comment by p4bl0 | Hacker News Reader

My sister lives in Switzerland, in a remote place in the mountain from a small town. Even over wifi the bandwidth at her place is so fast it made my BitTorrent client crash repeatedly. The solution was to disconnect my system by deactivating the wifi, relaunch my BitTorrent software, set a rate limit to the download speed at 30MB/s, and then reactivate wifi.

View on HN

30MB/s is not a lot. Which client was that? KTorrent can easily deal with more than three times that, which is what I get here in Poland on a plan that's not even the fastest one available.

It was KTorrent! But to be fair I just arbitrarily thought that 30MB/s would be more than enough speed (at my place in France that's probably the fastest my internet connection is capable of), tried that, it worked, in a few seconds the file was there, and that was it. I didn't try to see how fast I could go before a crash, maybe if I would have set it to 100MB/s it would have still been ok.

Seems like it would be good to move some of the stuff it does to a dedicated thread as I've noticed the UI freezing for some time when downloading a lot of data fast (but I believe it's more about my slow SSD than Internet speed). No crashes though!

I've had various pains with QBittorrent (nox) which seem to vary based on the version of the client and the version of libtorrent used. Out-of-memory and resume issues, but varying according to the torrent size, number of simultaneous downloads, and version/configuration specifics.

Torrent software (the clients and the libraries) feel a little out-of-sync with prevailing torrent sizes and bandwidth availability.

Reply on news.ycombinator.com