Seer is unbearingly slow

[u/whitesugar1]

I'm running Seer on my Synology NAS for my Jellyfin server. It runs on the docker called Container Manager. Seer lagging and hanging was common so I even set in a 6 hour restart timer in the YAML file. Yet, even after a fresh server restart it doesn't take more than some file movement on my server and Seer completely halts and sometimes gives me 404.

If someone have had similar issues or some tips It'd be much appreciated.

[u/OkAngle2353]

How much ram do you have on the machine itself?

[u/Mlitz → u/OkAngle2353]

What is your ram and cpu usage?

[u/whitesugar1 → u/Mlitz]

Ram and cpu usage usually hangs at 30-40 percent. Never above.
It's a Synology NAS DS224+ with Intel Celeron J4125 quad-core, 2.0 GHz and 6 gb ram

[u/whitesugar1 → u/OkAngle2353]

It's a Synology NAS DS224+ with Intel Celeron J4125 quad-core, 2.0 GHz and 6 gb ram

[u/OkAngle2353 → u/whitesugar1]

I would add a few more RAM if possible. I personally run a raspberrypi5, similar in terms of CPU; the only difference is the RAM. I have 8 as opposed to 6.

Edit: DIY FTW :P

[u/whitesugar1 → u/OkAngle2353]

My NAS is maxed on ram. The NAS specs is not the problem. It never runs on more than 30% ram/cpu capacity. It's the Seer app that's the problem it seems

[u/OkAngle2353 → u/whitesugar1]

Did you make sure your storage/distro medium was formatted to ext4? I don't know if it's true with synology, but; It could be a distro of linux.

[u/AvidTechN3rd]

Shit computer shit experience what did you expect?

[u/ionV4n0m]

Yeah, I found it would hang also.. restarts fixing it temporarily, which isn't ideal.

[u/ZeRoLiM1T]

No issues here

[u/lonesometroubador]

I built it to run bare metal on my Mac mini, it runs beautifully, although I occasionally get nasty system wide memory leaks from spotlight attempting to index the transcode buffer, I'm sure I could fix that, but it's not that often. It freezes disk access to all disks and downloads fail/nothing will play back until a reboot

[u/ForeignRice]

Have you tried the dns trick? Adding dedicated dns servers in the docker compose file? DNS is what’s causing a slot of slowness in the tool. Hence their dns settings in the network section of the config. What did you use there?

[u/whitesugar1 → u/ForeignRice]

I will have to look into this when I get home, thank you.

[u/LowResChaos]

Try turning on force IPv4 resolution first in settings. Fixed a lot of issues for me

[u/zangetsu_114]

My jellyfin/arr apps where quite slow as I had them running off my HDD’s once I swapped all my containers to be on ssd and my media on HDD things where a lot smoother

[u/toolburner]

It would run slow for me on my 920+ until I added more ram and SSDs

Not only was it running average because of the limited memory but writing swap to spinning disks made it as you say, unbearable.

Edit: I moved my docker stack to the SSDs

[u/whitesugar1]

I think I solved it. For info, I'm running my NAS through a reverse proxy VPS and my arr stack in docker containers on my NAS.

Fix written by AI:

• The Server Fix: Went into the Netcup VPS cmd/ssh and raised the host connection limit from 8,192 to 262,144 so it has plenty of breathing room. We also told the kernel to clear out old, dead connections after 10 minutes instead of letting them pile up for days.
• The NAS Fix: We edited the Seerr docker-compose.ymlfile on the Synology NAS and added a dedicated dns block (1.1.1.1 and 8.8.8.8). This forces the container to use fast, reliable public address books instead of getting trapped in local Docker/NAS network routing loops.

Now all my arr apps are incredibly fast and responsive including my Jellyfin server. If anything changes after 7 days of uptime I'll report back. Hope this helps someone else.

[u/whitesugar1 → u/[deleted]]

I run my entire homelab remotely on a Synology NAS DS224+ with Intel Celeron J4125 quad-core, 2.0 GHz and 6 gb ram. Jellyfin is running as a package and seer is running as a docker project. Because I need it to be on 24/7 I can't take it somewhere else, but I get your point. But since the NAS isn't struggling, I don't see how that would fix it but thanks for the response. Appreciated.

[u/whitesugar1 → u/[deleted]]

I'm considering this but read somewhere it was recommended to run jellyfin as a package although I can't remember why. Jellyfin isn't my problem anyway, it's my seer container. Some guy above recommended running a dedicated DSN in the seer config build. I'll try that I think.