autoscan VS qbittools

Use Cloudbox/autoscan instead. Plex Autoscan is not maintained anymore, you can see the repository is archived.

If you use *arr to manage your downloads try setting up the "Connect" section of it with Plex and only scanning when you import/add new media to save on the periodic scans for no reason, or perhaps check out https://github.com/cloudbox/autoscan as I've heard good things about this as well.

You should now use this instead: https://github.com/Cloudbox/autoscan

This tool is designed to let sonarr/radarr directly communicate with tdarr, much like autoscan is able to communicate between sonarr/radarr and plex/emby/jellyfin.

The solution to have plex refresh the metadata after a bazarr subtitle add is to use autoscan. NOT plex_autoscan, but autoscan. This is the newer version. You also need autoscan-adapter, the critical piece of the puzzle. Autoscan by itself lets bazarr/sonarr/etc notify plex to update libraries. The autoscan-adapter helps autoscan be able to actually refresh plex metadata so the new subtitles from bazarr can be found. This is all actually very easy to implement using docker-compose. Refer to the docker-compose setup in the autoscan-adapter github.

I recommand using Autoscan. If you're using the *arr stack to download your medias, it can then automatically trigger a scan. The *arr stack can do this without autoscan for jellyfin, but the advantage of autoscan is that you can plug it to any of your other means of downloading medias by just calling its webhook

Until then you can use something like qbittools and run it with re-announce on an interval.

Might be worth checking this out: https://gitlab.com/AlexKM/qbittools

If you don't want to mess with any of this; then maybe you can set max: 1 downloads per hour on your filter settings. Not as ideal as using a tool like qbittools or qbittorrent-cli, but it should still help with HDD I/O. But then again, rTorrent is not ideal for racing torrents.

A category for your *arr downloads. One for for your racing on your /ssd, and another for files to permaseed on /hdd. These Categories then can be managed by other third party tools. One example that I use is called qbittools which has a "mover" function.

Other than that you don't need much for TL. I would only suggest that you implement some kind of solution to not hammer your disk I/O by trying to race too many torrents at once, especially if it is an HDD. I guess as an easy solution, you could do General > Max 1-2 downloads per hour. Better yet, if you use qBittorrent, you can use something like qbittorrent-cli or qbittools to limit the amount of concurrent races to 1-2 or whatever you think is fit.

Tool to inject and re-announce using qBittorrent

Setup this to run hourly via cronjob and every torrent with whatever tracker you add to it, you can pause it.