Jellyfin feels quite slow and buggy

[djego]

Hi, everyone!
I'm probably not the first one that started migrating from Plex since last policy changes, but I'm happy to finally take a step towards an open source project like this.
Anyway, I have an issue: whenever I try to browse my Jellyfin library, everything seems so slow and unresponsive. Even sometimes I have problem loggin in (even from local). I'm not sure if it's a problem generated by how I config everithing or some incompatibility yet, but I'll try to give you guys all the info, since I'll love to fix it:
I'm running jellyfin 10.10.5-01 in a TS-230 NAS, via pdulpvp qpkg (https://github.com/pdulvp/jellyfin-qnap/...1_466293ab).
I'm using a DuckDNS domain and a nginx container (in order to set a reverse proxy and have it accessible via HTTPS).
My library is the same as the Plex one, being Plex still active.
I set up all this aided by some Youtube videos and some ChatGPT help, since I didn't want to annoy anyone, so maybe some of my setup is not properly configured. I wouldn't have a lot of issue if I have to start everything again, to be honest.

The issue, as I said, is that everything seems so slow (okay, here I tried to open some video file and checking how long it took, but Jellyfin didn't even open, and this also happens sometimes, in web browser, Windows client and Android one too).

Maybe I should use a docked solution instead a prepackaged qpkg?

Sorry for the trouble and thank you everyone.

Quick edit: my goal is to have it set for my use and some friends, so I configured it to also have remote access, but most of my tests have been local. Also, for some reason, Plex has now more issues (only when Jellyfin is active in my NAS).

[damsdams]

Hello, just like you, I find it very slow. After searching everywhere, I discovered that the database system is very poorly designed. Everything relies on a single file that can only handle a few requests. Personally, I have a huge database to process, and unfortunately, Jellyfin's system is not suitable for this. My migration from Plex to Jellyfin cannot proceed, but I saw that they are working on the database issue.

Same here, I also did tests on Android and Android TV, and it's the same issue. Everything goes through the database file, so when there are too many requests to the file, it's impossible to connect.

ps google traduicion me french

[djego]

Is it because database should be in a SSD? That would be the issue, then, since I have two HDDs on my NAS, no SSD.

[damsdams]

Nope, I have an SSD. I put all the data like config, storage, miniatures, etc., to make sure I don’t have any storage issues. Even the database was on the SSD.

[damsdams]

But basically, it was saying "database is locked" because everything is managed in a single DB file, so it gets saturated quickly.

[TheDreadPirate]

The database should definitely be on a SSD. Depending on what else you have your NAS doing, now it has to run a database as well?

Regarding the playback issues, it sounds like it might be transcoding but you didn't setup hardware acceleration?

Can you share your jellyfin logs via privatebin.net?

[djego]

Hi, I tried reinstalling again (current version now) and it's a bit better, but still it sometimes drop my conection and have to reenter. Also, I think now my problem is with transcoding: I tried to run it like my Plex server (no transcoding, since my NAS' CPU is quite weak), and it seems that I have two options: either transcoding (99% CPU, and it doesn't start) or not doing it (and then I just cannot see whatever I tried to play). It's a bit weird, since I'm using H.264 mp4s.

[TheDreadPirate]

I'd have to see your logs to see what it is doing.

[djego]

It's here: https://privatebin.net/?e3c0a6668520af91...7Wx2CkUWEM

[TheDreadPirate]

Try setting the jellyfin container to host networking mode.

Not sure if this is also contributing the the sluggish-ness, your server was in the middle of a library scan. So that would consume quite a bit of resources. Since your NAS has a pretty slow ARM CPU, it doesn't have much to begin with. Responsiveness should improve on the system after that library scan finishes.