Page 1 of 1

Optimal Settings for Maximum Seeding Speed?

Posted: Sun Jul 29, 2018 8:15 am
by blerns
System Specs:
CPU: Intel Core i7-8700K
MOBO: ASRock Z370 Taichi
RAM: 16GB DDR4-3200
SSD: Samsung 970 PRO 512GB
HDD: HGST 6TB

OS: Windows 10 Home x64 (Version 1803, build 17134.191)
Connection: http://dfkrkqaqb1zsx.cloudfront.net/spe ... 607184.png (Down: 945Mb/s, Up: 41.5Mb/s)
qBittorrent: 4.1.1 64bit (Qt: 5.10.1, Libtorrent: 1.1.7.0, Boost: 1.67.0)
Ports are open, and qBittorrent shows Connection Status as Online/green.

What are the optimal settings in qBittorrent to (aggressively) seed at my connection's maximum speed? I want to max out my upload whenever possible, without regard for the connection being usable for anything else.

I don't have any issues with download speeds on qBittorrent, but for some reason I seem to have issues seeding as well as I do on uTorrent. uTorrent seems more aggressive/quicker in connecting to peers to seed to, and I'm able to send at my connection's limit very easily (peers permitting). On qBittorrent, it seems way slower to connect to peers to seed, and my upload speeds are really poor, even on new torrents with many leechers that I am one of the few seeders on. Sometimes qBittorrent will start out seeding to a peer at a decent speed like 2MB/s, and then within a minute (usually 10-20 seconds), slow down to 10-30KB/s (it doesn't always do this, but usually I don't seed much faster than 500KB/s) I'm curious if there are better settings I could be using that could help utilize my connection fully.

Current settings:
https://i.imgur.com/f2Xy5j1.png

Re: Optimal Settings for Maximum Seeding Speed?

Posted: Sun Jul 29, 2018 11:31 am
by Adsixnine
??? ??? ???

Re: Optimal Settings for Maximum Seeding Speed?

Posted: Sun Jul 29, 2018 2:23 pm
by Switeck
Wait for qBitTorrent to start using Libtorrent v1.1.8 or later and maybe some of these problems would magically go away.

But until then, try...

In advanced settings...
Disable Resolve Peer Countries (GeoIP) due to:  https://github.com/qbittorrent/qBittorr ... -408591923
Disable Download tracker's favicon (less load on trackers, especially nice if you're constantly updating 5+ trackers on 100+ torrents).
Increase disk cache duration from default of 60 seconds (before it "forgets everything"!) to 600 seconds (which is still a pretty short-term memory).
Raise Send buffer watermark to 1000 KB. (This helps reduce pipeline stalls.)
Raise Send buffer watermark factor to 100 KB. (This REALLY helps reduce pipeline stalls.)
Lower Maximum number of half-open connections to 10. (This has NO effect on how fast incoming connections come in, which is how you'll get the vast majority of your connections except maybe to not crowd them out with dead and duplicate connections.)
Disable Always announce to all trackers in a tier (Some torrents that have tracker tiers sometimes have them to keep you from getting banned for over-announcing to sub-trackers that point to the same server. Also slightly reduces load on trackers and it's why it's a bad idea to add similar/duplicate trackers to a torrent.)

Outside of advanced...
Your connection has about 4800-5000 KB/sec total usable upload speed, and that's assuming it's stable at that speed. (It is ComCast after all, one short 5-100 minute outage a week is expected!)
Spread 5000 KB/sec evenly between 500 connections and that's 10 KB/sec each at best. When it's maxed out, a peer that connects to your seed only on a single torrent will look about 2x as good as 56k dial-up.
You could probably upload more KBs and at a slightly faster KB/sec speed (closer to max) by lowering global and per torrent max values from 500/100 to about 300/30. If you're only seeding, 100 connections per torrent can mean a handful of torrents could "hog" most of the connections and cause other seldom or barely active torrents to "starve".
It really depends on how busy your torrents are -- you may only have 1 torrent that regularly gets over 50 peers at the same time or you may have lots that get >30 peers at once.

Even 10 connections per torrent when you have LOTS of seeding torrents is plenty.
Now admittedly 10 connections can seem a little low while downloading, but that's why this was requested:
https://github.com/qbittorrent/qBittorrent/issues/2193

Re: Optimal Settings for Maximum Seeding Speed?

Posted: Sun Jul 29, 2018 6:44 pm
by blerns
Thanks for the suggestions, Switeck. I've applied the settings.

Re: Optimal Settings for Maximum Seeding Speed?

Posted: Thu Nov 07, 2024 8:11 am
by ssateneth
At the risk of getting yelled at for thread necro, would these settings be good for a vastly faster setup? I got a 5gbps fiber connection (both up and down get the same speed) and i have about 2.5tb of material across 450 active torrents that i rotate seeding on depending if i've reaching a high seed ratio or not. It regularly seeds about 100-200MB/sec but I've seen about 400MB/sec on a popular torrent that recently got released. I can easily saturate the download, about 600 MB/sec, but I'm having a hard time saturating my upload. It's like it doesn't want to connect to peers. I have unlimited connections for everythign in the collection limits section of the connection settings (not advanced). do you have any recommendations on how to increase the amount of peer connections and upload?

it's also possible i'm being CPU limited - qbittorrent is pegging 1 cpu core to 100% but I have 16 cores.
Switeck wrote: Sun Jul 29, 2018 2:23 pm Wait for qBitTorrent to start using Libtorrent v1.1.8 or later and maybe some of these problems would magically go away.

But until then, try...

In advanced settings...
Disable Resolve Peer Countries (GeoIP) due to:  https://github.com/qbittorrent/qBittorr ... -408591923
Disable Download tracker's favicon (less load on trackers, especially nice if you're constantly updating 5+ trackers on 100+ torrents).
Increase disk cache duration from default of 60 seconds (before it "forgets everything"!) to 600 seconds (which is still a pretty short-term memory).
Raise Send buffer watermark to 1000 KB. (This helps reduce pipeline stalls.)
Raise Send buffer watermark factor to 100 KB. (This REALLY helps reduce pipeline stalls.)
Lower Maximum number of half-open connections to 10. (This has NO effect on how fast incoming connections come in, which is how you'll get the vast majority of your connections except maybe to not crowd them out with dead and duplicate connections.)
Disable Always announce to all trackers in a tier (Some torrents that have tracker tiers sometimes have them to keep you from getting banned for over-announcing to sub-trackers that point to the same server. Also slightly reduces load on trackers and it's why it's a bad idea to add similar/duplicate trackers to a torrent.)

Outside of advanced...
Your connection has about 4800-5000 KB/sec total usable upload speed, and that's assuming it's stable at that speed. (It is ComCast after all, one short 5-100 minute outage a week is expected!)
Spread 5000 KB/sec evenly between 500 connections and that's 10 KB/sec each at best. When it's maxed out, a peer that connects to your seed only on a single torrent will look about 2x as good as 56k dial-up.
You could probably upload more KBs and at a slightly faster KB/sec speed (closer to max) by lowering global and per torrent max values from 500/100 to about 300/30. If you're only seeding, 100 connections per torrent can mean a handful of torrents could "hog" most of the connections and cause other seldom or barely active torrents to "starve".
It really depends on how busy your torrents are -- you may only have 1 torrent that regularly gets over 50 peers at the same time or you may have lots that get >30 peers at once.

Even 10 connections per torrent when you have LOTS of seeding torrents is plenty.
Now admittedly 10 connections can seem a little low while downloading, but that's why this was requested:
https://github.com/qbittorrent/qBittorrent/issues/2193

Re: Optimal Settings for Maximum Seeding Speed?

Posted: Thu Nov 07, 2024 8:23 am
by Peter
ssateneth wrote: Thu Nov 07, 2024 8:11 am...
- if you are port forwarded and its working, you should be good. peers not always want to connect to every other peer.
- make sure encryption and uTP are both enabled (not forced but enabled so you can connect to both).
- use NVME SSD drives so you can read that much. 600MB/s speed will put a serious heat strain on it so a heat sink might be needed as well. you can check heat in HWINFO.
- you might get better stats if you enable "Simple pread/pwrite" in Advanced on the latest 5.0.1 version. or you can try using the NOT lt20 variant.