- 5 Kwiecień 2008
- 10 437
- 2 641
- 405
- Odznaki
- 205
- QNAP
- TS-x77
- Ethernet
- 1 GbE
Poz.
6
Symptoms
Cause
A downloading torrent connects to new peers on its own only while it has fewer than its minimum number of peers. Above that minimum, it only accepts peers that connect to it, up to its maximum. A peer that stays connected but sends nothing still occupies its place. When such peers fill the torrent, its speed falls even if faster sources are available.
Rtorrent 16 has peer rules to prevent this, and they are on by default. A downloading torrent closes peers that have left it waiting for 5 minutes. When a download is stuck (two checks in a row brought less than a tenth of its best check in the last ten minutes, or less than 2 KiB/s), it closes them after 90 seconds. A closed peer cannot connect again for 30 minutes. Every 30 seconds, a torrent with all its download slots taken gives the slots held by its slowest senders to waiting peers.
Resolution
Notice & Advise
With rtorrent log level set to notice (the default), rtorrent.log gets a line with "dropped … idle peers" each time the first rule closes peers. Open it in Diagnostics, under Logs.
Ref. links:
Rtorrent 16 guide: Public and private connection profiles
- A torrent downloads fast at first, then drops to a few KiB/s and stays there.
- The torrent holds many peers, but almost none of them send anything.
Cause
A downloading torrent connects to new peers on its own only while it has fewer than its minimum number of peers. Above that minimum, it only accepts peers that connect to it, up to its maximum. A peer that stays connected but sends nothing still occupies its place. When such peers fill the torrent, its speed falls even if faster sources are available.
Rtorrent 16 has peer rules to prevent this, and they are on by default. A downloading torrent closes peers that have left it waiting for 5 minutes. When a download is stuck (two checks in a row brought less than a tenth of its best check in the last ten minutes, or less than 2 KiB/s), it closes them after 90 seconds. A closed peer cannot connect again for 30 minutes. Every 30 seconds, a torrent with all its download slots taken gives the slots held by its slowest senders to waiting peers.
Resolution
- Check the torrent's sources. In Quick access, the row shows how many seeders you are connected to and how many the tracker reports. When the swarm has only a few seeders left, no setting brings the speed back.
- Check the peer rules. Open Settings → Connection profiles and press Custom…. Under Peer rules, Close peers that keep a download waiting, Close idle peers sooner while a download is stuck and Rotate a full set of download slots should be on. If a field reads rtorrent runs …: a line of your own in rtorrent.rc sets it, its value comes from the line you added to rtorrent.rc.
- If peers that send very little are holding the torrent back, open Settings → Connection and, under Slow peers, turn on Disconnect very slow peers (off by default). Every 5 minutes it disconnects up to 5 peers slower than Slow below (KiB/s) from a download that has its full number of peers while others wait. They can connect again. Compare the speeds of your torrents before you leave it on.
Notice & Advise
With rtorrent log level set to notice (the default), rtorrent.log gets a line with "dropped … idle peers" each time the first rule closes peers. Open it in Diagnostics, under Logs.
Ref. links:
Rtorrent 16 guide: Public and private connection profiles