Comment on Sonarr (dev) now supports postgres
gabriele97@lemmy.g97.top 1 year ago
What are the advantages of using postgres? It makes radarr/sonarr faster?
I was curious too, so I looked into their Github issues. Apparently, SQLite doesn’t play well with k8s due to the distributed/networked nature of the environment. According to comments in the pull request, that seems to be the main driver. And apparently, Radarr already has a Postgres option.
Though, there are requests going back to 2017 to support it…just because, I guess? That person seems to just want all their data in one DB for some reason.
SQLite doesn’t like NFS, the file locking isn’t stable/fast enough so any latency in the storage can cause data loss, corruption or just slow things down.
However SQLite to MySQL is relatively peanuts, Postgres less so…
Still it’s a nice move for those that don’t run containers on a single host with local filesystems.
Basically this. I have my home stuff running in a K3S cluster, and I had to restore my Sonarr volume several times because the SQLite DB has corrupted. Transitioning to Postgres should solve this issue, and I already have quite a few other stuff in it, for example Radarr and Prowlarr
Longhorn storage, ceph block, or other distribed BLOCK storage can help assist this issue.
Yeah I’m using Longhorn. Might be that I have set it up wrong, but didn’t seem to have helped with the DB corruption issue.
Khaelas@lemmy.world 1 year ago
I have this same question. I’m running Emby, Sonarr, Radarr and Sabnzbd on a 16GB RAM 4 year old laptop and it seems just fine performance wise. What could I be missing out on?