How Rtorrent 16 is built: what comes first
Rtorrent 16 is made for fast downloads, strong seeding and private trackers on a QNAP NAS.
This page lists what weighs most when we decide how Rtorrent 16 works, and the questions a feature request is judged by. The facts on it are defaults of the current release.
- HighestDownload and seeding speed, private trackers, security, performance, professional setups and large archives
- MiddleSlower devices and slower internet, public torrents
- LowestQueueing, requests for one network or setup, setups that change the default config
Three weights
A request that serves a higher weight goes first. A request that costs a higher weight something does not go into the defaults.
Highest
- Download and seeding speed. No download or upload speed limit is set by default, and rtorrent may use up to 2,048 MiB of memory for pieces.
- Strong seeding. The download queue holds only unfinished torrents. A finished torrent never waits for a place.
- Private trackers. A private torrent never gets the public tracker list, DHT or peer exchange. To trackers Rtorrent 16 reports rtorrent 0.16.25, a version that private trackers which allow clients by exact version accept.
- Security. An outside address is blocked after 5 different wrong passwords within 5 minutes; local network and Tailscale addresses are exempt. The only telemetry is the daily update check, and one switch turns it off.
- Performance and large archives. Rtorrent 16 raises rtorrent's open-files limit to 65,536. On our test NAS that left up to 60,672 sockets for peers, enough for a session of 10,000 torrents.
- Professional setups. The Dashboard's Peers and their limits card shows the limits rtorrent runs with now, beside the ones saved in Settings.
Middle
- Slower devices. Rtorrent 16 has a build for Intel and AMD processors (x86-64) and one for 64-bit ARM.
- Slower internet. Connection profiles set the peers per torrent and how many peer addresses each announce asks for, separately for private and public torrents.
- Public torrents. A new public torrent gets up to 16 public trackers in 4 groups, and DHT and peer exchange are on.
Lowest
- Queueing. By default no download waits in a queue. Max active downloads (experimental) works only with Developer mode on.
- Requests for one network or one setup. They do not change the defaults. Extra rtorrent.rc lines make such a change on the NAS that needs it.
- Setups that change the default config. rtorrent reads your own lines after the panel's lines, so a setting you write there is the one it uses.
How a feature request is decided
We ask five questions in this order. The first answer that fits decides; when none fits, the owner decides.
Is it faster, or does it keep a private tracker's rules?
A change that makes downloading or seeding faster, or that a private tracker requires, goes ahead first.
Is it safer, or does it use less of the NAS?
It goes ahead if downloading and seeding stay as fast.
Does it help slower devices, slower internet or public torrents?
It goes ahead if it slows nobody else down.
Would it slow the defaults for everyone to fix one network?
It does not go into the defaults. You make that change on your NAS, in Settings or in Extra rtorrent.rc lines.
Is it a queue or a delay?
It stays behind Developer mode or out of the package.
The defaults are not imposed
The ready setup follows three things: what users report, what trackers require, and what Plex, Kodi, Jellyfin and Emby need from the folders and the library.
You change the defaults on your own NAS:
- Settings → Connection profiles, Custom: peers per torrent and peers asked from each tracker per announce, for private and public torrents.
- Settings → Connection, with Advanced on: DHT, peer exchange and the public trackers added to new public torrents.
- Settings → Advanced → Extra rtorrent.rc lines: commands the installed rtorrent accepts. They are added at the end of rtorrent.rc, after your own .rc files and rtorrent.rc.local.
Before you ask
Will Rtorrent 16 get a switch that starts torrents one at a time?
No. A queue at start delays every torrent behind it, at every start, and speed weighs more than a queue. We measured the start instead: with 500 public torrents and the public tracker list off, Rtorrent 16 made up to 41,000 connection attempts in its first 10 seconds when no peer answered, and 3,076 in the first minute with 16 real public torrents.
If your network needs fewer connection attempts at start, change it on your NAS. The next answer shows where.
My provider cuts my internet when Rtorrent 16 runs. What can I check?
A burst of connection attempts can make some providers cut the line. Check these places, in this order:
- Dashboard → Peers and their limits: how many sockets rtorrent holds now, and its limit.
- Settings → Connection, with Advanced on: set Add public trackers to new public torrents to Off and save. It applies to torrents you add from then on.
- Settings → Connection profiles, Custom: lower Public: peers each tracker is asked for and max in Public profile: peers per torrent.
- Settings → Advanced → Extra rtorrent.rc lines:
network.max_open_sockets.set = 4096. With 2,000 public torrents and the list off, it cut the busiest 10 seconds from 60,672 connection attempts to 4,475.
We cannot change a provider's flood protection. The measurement and the effect of each setting are in the article linked below.
Why does a private torrent not get the public trackers?
A private tracker can forbid other trackers and ban the account that announces to them. So a private torrent keeps only the trackers it came with, and DHT and peer exchange stay off for it.
Can I set it up my own way?
Yes. The defaults are settings you can change, and Extra rtorrent.rc lines take the commands the installed rtorrent accepts. rtorrent reads them when it starts.
Why is the download queue only in Developer mode?
Queued downloads wait for a running one to finish or stop, even while the running ones barely move. That costs speed, which weighs most.