Well, here I have 41 containers and:

free -hm
               total        used        free      shared  buff/cache   available
Mem:            31Gi       5.7Gi       426Mi       207Mi        25Gi        25Gi
Swap:           31Gi       3.7Gi        28Gi

As well as

cat /proc/sys/vm/swappiness: 10

and

$ cat /proc/pressure/cpu
some avg10=0.00 avg60=0.00 avg300=0.00 total=302436406
full avg10=0.00 avg60=0.00 avg300=0.00 total=0

$ cat /proc/pressure/memory
some avg10=0.00 avg60=0.00 avg300=0.00 total=64263542
full avg10=0.00 avg60=0.00 avg300=0.00 total=63043120

$ cat /proc/pressure/io
some avg10=1.99 avg60=1.67 avg300=1.61 total=1844790000
full avg10=1.90 avg60=1.59 avg300=1.56 total=1788451770

I agree with you that my server specs are a little bit excessive for my usual workload. I have disabled swap in the past with swapoff -a and removed the partition from /etc/fstab under a similar usage, and no issues were observed.

I am just leaving it there now for the rare instance when I run the occasional lightweight local LLM model (on CPU) for light tasks such as spell checking, which might need some RAM and I don't risk crashing due to OOM issues.

However, I still want to understand what is happening here to learn a little bit about my system. My intuition can be wrong here, but I find it strange that my laptop with similar specs and the same OS (but reasonably distinct workloads, to be fair) almost never swaps nor reaches those ridiculous levels of buffer + cache usage, so I think I might find one "offender" container to blame.

Thanks for the tip. I have been looking into commenting out the ollama portion of the docker-compose.yml file and setting up llama.cpp instead for some time now. I suspect I don't usually use features such as ollama pull to justify a fully-featured application.

I would like to keep it to torrents, since it doesn't hurt to improve my setup's resilience (after all, why not, right?). But at the same time I suspect that usenet might improve my experience, according to what I have been reading online when trying to debug this problem I'm facing.

You are right about the crack in my investigation. It seems like I have to dig deeper, and this is another indicator that maybe the usenet solution would be my best bet here, since I have already added plenty of indexers. You raise a good point about the filters configured in the *arr stack perhaps being "too aggressive" and sleeping on what would be a "good match". I will look into that.

I do have a specific example of content my setup isn't finding. I will give it a look later to find a specific season/episode that matches the criteria and report back. I appreciate your willingness to help!

If I do a manual search on public indexers (1337x, TBP, etc), I do not find the results I'm looking for. That means I would be out of luck following the standard process.

I am not using the same indexers on prowlarr and stremio. I actually do not use stremio, and from what I found online, they use addons and plugins like torrentio are responsible for doing the heavy lifting. My suspicion is that they rely on private indexers that I'm yet not aware of. By comparing magnet links from my friend's stremio setup, many of these results actually seem to be available at private indexers.

I will keep this in mind, since I strongly suspect that usenet would seriously improve my experience, and comments here seem to corroborate that idea. I appreciate the tip!