The library scan took 3 hours for around 6k files. Plex takes much less time than that. There are many people raising this issue for years now but it is still not fixed.

From the logs I see Jellyfin trying to extract images for chapters even though the option isn't checked. I already found reports for such issues but they are closed without an answer.

The big problem for me is Jellyfin not starting and getting stuck (without meaningful logs) at startup each time the server is shutdown. I did the reinstall 5 times now and trying the native install now. From the debug logs it seems like Jellyfin is stuck on one sql query.

From what I have seen, many issues are getting closed because of non activity even when the issue is still there.

I know that the project is done by volunteers but I was just wondering whatever I should invest more time on trying to resolve the issues. Maybe my server specs are just not ideal for Jellyfin.

you are viewing a single comment's thread
view the rest of the comments

[–] ShortN0te@lemmy.ml 1 points 1 month ago

I saw that they are working on big refactoring to use EFCore instead of doing direct SQL queries. I actually was surprised when they were saying that the migration will take days for some, and you shouldn't interrupt it.

That you should not interrupt a database migration is really standard procedure. If it takes days is unfortunate, but what should the devs do? Create a migration process with weeks and months of testing that can recover after a interruption, for those 3 ppl that run on slow hardware?

Pls do not get me wrong, that the database and everything related to it is slow and basically legacy code is not good, but exactly that is beeing worked on right now, instead of continuously pumping out new features. Complaining about the exact thing that is currently in the works feels very disingenuous.