mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Only 1 core at 100% #441
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Sirfrancis17 on GitHub (Feb 19, 2019).
Hi
I do not know why but Jellyfin only uses me 1 core and this is always at 100% (Just watching the movie list)
When you enter the Web page and select My library, Jellyfin takes about 15 seconds to load the page (list 100 movies) is it normal to be so late?
What can be the mistake?
I use Docker (v. Jellyfin 10.2)
@ddurdle commented on GitHub (Feb 20, 2019):
Emby has always been a single threaded server application. JellyFin hasn't fixed this issue yet.
@Sirfrancis17 commented on GitHub (Feb 21, 2019):
I added my movie library (gdrive + rclone) to Jellyfin. It has finished the indexing taking more than 1 day.
Now every time I enter the movie section takes more than 15 seconds to show the content (100 movies for page)
Every time go next page (Library) it takes more than 15 seconds.
Also, when I update the library it usually takes hours (no new file)
This is normal? I say that because in Emby (v4) load the movie page is 1-2 seconds and updating the library takes a few minutes
@cvium commented on GitHub (Feb 21, 2019):
@Sirfrancis17 it's far more interesting to know if Emby 3.5.2 is faster.
@ddurdle commented on GitHub (Feb 21, 2019):
I use Google Drive content and Jellyfin but have no performance issues as such. Library updates are very fast.
@Sirfrancis17 commented on GitHub (Feb 21, 2019):
It's weird. @ddurdle You also use the Docker version?
@NotExpectYet commented on GitHub (Feb 25, 2019):
Mine's worse for loading my 17TB library. Once the dashboard is filled with information it's rather snappy, but takes about 2-3 minutes for that to full load with artwork. I'm on docker, latest version on unraid
. Can do a clean boot and load of the library for logs if it will help?
@Sirfrancis17 are you waiting for the dash to full propagate before clicking into a library?
@hawken93 commented on GitHub (Mar 10, 2019):
what kind of CPUs are this? Are these especially slow CPUs or are they desktop / server class? on my 10.2.0 install on 2GHz xeon, a page load leads to some cpu usage but it does jump above 1 core and it doesn't feel laggy. But maybe on older hardware this is exposed as being laggy?
@Sirfrancis17 commented on GitHub (Mar 10, 2019):
Its a amlogic S912 octa core corte a53 64bits
El dom., 10 mar. 2019 11:14, hawken notifications@github.com escribió:
@hawken93 commented on GitHub (Mar 10, 2019):
I've looked them up and in single core performance one of these are around 5-6 times slower than what I run jellyfin on so your delays could be up to 5-6 times as long I think..
https://browser.geekbench.com/v4/cpu/11882434
developers can simulate this a bit by using cpulimit to check if it leads to the same behavior.
This is just a rough estimate though, and maybe some dotnet implementation details could also be a factor here?
Either this, or something weird is happening with the library or something.. I think profiling jellyfin would be the way to go.
We know that the server does too much computation upon the http requests, but having some profiling would help with finding out what needs to be optimized first. :)
@hawken93 commented on GitHub (Mar 10, 2019):
Does jellyfin go back to idle when you leave it idle? How long does it burn cpu for when you hit it with a refresh?
@Sirfrancis17 commented on GitHub (Mar 10, 2019):
Yes.. If jellyfin not work the cpu its 5-10%
When refresh, the cpu burn at 100% but only 1 core from 8 (cpu have 8)
@Bond-009 commented on GitHub (Mar 10, 2019):
This should be fixed by #1011