I don’t do anything with it, pure set and forget. I probably should, I don’t use XXX at all. NSFW is under a different stack, different gluetun, and different network namespace. As for size, I don’t know but I found this in the FAQ:

What are the system requirements for bitmagnet?

As a rough guide, you should allow around 300MB RAM for BitMagnet, and at least 1GB RAM for the Postgres database. You should allow roughly 80GB of disk space per 10 million torrents, which should suffice for several months of crawling, however there is no upper limit to how many torrents might ultimately be crawled. The database will run fastest when it has plenty of RAM and a fast disk, preferably a SSD.

I run one because why not. I’ve set it as No1 priority in Prowlarr, with the same requirements as any other indexer. BitMagnet is currently second for successful grab count.

I just set and forget it, reccomended compose. Bind mount the DB to a NVME and let it do its thing. It’s at ~20m entries currently and isn’t climbing much from there. Although it’s No1 priority I consider it a back up so I don’t give it too much attention if I’m honest.