This is an automated archive made by the Lemmit Bot.
The original was posted on /r/piracy by /u/quentech on 2025-08-24 22:22:08+00:00.
I used to be a member on a private tracker, RevoTT, for many, many years. Occasionally I'd grab some stuff off public trackers - RARBG, YIFY, etc.
I have 1Gbps dedicated fiber. Hundreds of TB of drive space, mostly full. Multiple 10's of thousands of torrents seeding.
RevoTT went through some concerning changes in leadership at the beginning of the year, so I started looking for alternative places to acquire content, and I got signed up on TorrentLeech and have been using that. Got a few TB downloaded already.
So here's the problem:
Whenever I'm early to a torrent on TorrentLeech - especially FreeLeech ones (which are often large 4k or 1080 remux) - the speed on all of my torrents completely tanks.
Instead of mostly or completely maxing out my 1Gbps WAN, like normal, I only seem to get data in short little bursts.
I'll get 10-20 Mbps for a second or two - and then close to nothing - maybe 10 or 20 kBps - for 10, 20, 30 seconds. Then another little burst of data. Then crawl. Then burst. Then crawl.
It does this until the offending torrent completes. Like, I can shut down qBitTorrent and completely reboot the Windows VM and even the hypervisor host it's running on. I can remove the torrent, delete all the files, and re-add it. Same problem.
When it boots back up and starts back up - I sometimes will see it going full speed for like 30 seconds or less - and then it's right back to the start & stop crap. It also makes the "Checking" of all the torrents while qBit starts up go extremely slowly while the bandwidth issue is happening.
While this is happening, I can max out my 1 Gbps WAN on a speed test. I can max out the 10Gbps internal network between the VM and the storage array. I can write to and read from the storage array at hundreds of MBps. Nothing else seems affected.
Again, when this happens, it happens to all torrents from any tracker. I've tried 4 other trackers while it's happening. Also my upload experiences the same problem - little harder to see because it depends if anyone's trying to DL - but with ~30,000 torrents there's almost always seeding activity on my box.
Hours and hours later, the offending torrent will finally complete, and then everything goes back to normal.
I'm totally lost as to WTF is possibly going on here. The other thing I notice is that the qBitTorrent app itself often gets quite laggy in response to any interaction with the GUI on the VM while this is happening.
Plenty of RAM on the machine, I've got 12GB assigned to the VM and qBit uses ~3GB. Drive activity is low on the VM, hypervisor, and storage array. It's assigned 6 CPU cores on a i7-11700 - plenty.
And here's another hitch - if I uninstall the standard qBit install and instead use the libtorrent 2.0 QT6 build - then this issue doesn't seem to happen. However, I get far, far fewer peers connecting to me than I'm used to with the libtorrent 1.2 build of qBit. This is noticeable on TorrentLeech, but it really stands out on RTT where I more often than not can't even complete download of a torrent when using libtorrent 2.0 because pretty much no other peers connect to me.
What in the everloving fuck is happening to me? It's making it really hard to build ratio when I can't ever DL a fresh torrent when it's early to the site.