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 3 points 2 months ago (2 children)

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.

Why do you think they do not?

If you would look up what they are actually doing, you woulf realize that a lot of work is done to improve the underlying quality of code to make it easier to do major changes to core functionality. Quick and dirty fixes by the previously project, emby, has led to a very shitty code base that makes changes hard.

[–] Underwire@lemmy.world 0 points 2 months ago (1 children)

I thought that the specs are not ideal for Jellyfin as it get stuck at startup, and it takes 3h to do a full scan. My server has an AMD Athlon II 2 220 Processor, 4 GB of RAM, so I thought that maybe Jellyfin need more.

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.

Jellyfin has many advanced features compared to Plex, but the experience isn't great for many. For example, Plex and Jellyfin allow you to match/identify your media. Jellyfin allow searching by IMDB/TMDB/… IDs, but Plex doesn't (possible by hidden way). But Jellyfin doesn't autofill the search and year fields, and Plex does. When you select a result, Plex instantly show the fetched details and does the rest in the background. Jellyfin will start rescanning the whole media or episodes, and you get a spinner until it finished checking all media/episodes (minutes later for me for some shows with many seasons). They are really small details but make the user experience not ideal.

[–] 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.