BakaBT > Need Help? Ask Here

Queued Seeding, Red Seeding Bar, Number of Connections

<< < (3/3)

Bozobub:

--- Quote from: Freedom Kira on October 09, 2012, 04:58:35 AM ---That can screw up the queue, actually. If you're running enough torrents and enough of the torrents keep connections alive without any activity, nothing ever gets done.

The more torrents you run, the smaller you should set the per-torrent max.
--- End quote ---
Not really.

First off, most of the  whitelisted torrent clients are decent at prioritizing connections.  Actively downloading torrents get most - in fact, nearly all - of the available connections, unless you manually specify otherwise.  When I run uTorrent, for example, with many torrents active, the client is pretty good at balancing the number of connections per torrent, within reason.  There IS, of course, some variability.

Second, your computer won't bog under ONE torrent using many connections any more than it will under MANY torrents using the exact same number of connections.  In fact, it will bog (slightly) more when many torrents are active.  The only thing allowing more connections per torrent will do, is let fewer torrents grab more connections per torrent, without you having to constantly change the number of connections per torrent.  In other words, you don't have to micromanage as much.

Try it yourself; empirical observation FTW.  I've observed the same behavior under uTorrent and Azureues/Vuze.

Freedom Kira:
The default for KTorrent is to not dynamically change torrent priority in the queue. This behavior initially had no problems, but once I went over 300-400 torrents, new torrents I added never even started downloading. BakaBT torrents stalled at 0B downloaded for days on end and never moved until I did something about it.

There's a setting that makes KTorrent shift stuff down the queue when they've been stalled for a long enough time, which is probably what uTorrent and Vuze do by default.

Vuze also has a feature where it does not count connections using less than a certain amount of bandwidth (like 256B/s or something), which is also useful for avoiding such situations. uTorrent might also have something like that. But for the general case, what I've said will hold true. Your client may have mechanisms in place to avoid lockups, but regardless it's not a good idea to allow as many connections per torrent as the client is allowed total if you are running more than, say, 10 torrents at a time.

Bozobub:
What you should be saying, then, is that you shouldn't do so, IF your torrent client doesn't prioritize connections properly =o .

Freedom Kira:
Perhaps. But you don't wait until your brakes fail before getting them fixed, right? It's a good idea to just set it that way regardless, sort of as a precaution.

ConsiderPhlebas:

--- Quote from: Freedom Kira on October 11, 2012, 10:23:56 PM ---Vuze also has a feature where it does not count connections using less than a certain amount of bandwidth (like 256B/s or something), which is also useful for avoiding such situations.
--- End quote ---
This is very useful, but you should make sure to change the actual value to something relevant to your bandwidth.
I've set mine to 5 kB/sec as more realistic for my connection (and not running hundreds of torrents, rather 15-30).

Navigation

[0] Message Index

[*] Previous page