2025-12-07, 11:36 AM
(This post was last modified: 2025-12-07, 11:38 AM by eomanis. Edited 2 times in total.)
That looks better than what I am getting.
I presume all the CPU work goes into database shenanigans. My data/jellyfin.db is 1.6 GB and I don't know if SQLite was ever meant to grow that large.
Maybe once Jellyfin supports PostgreSQL or another more optimized DB engine things will speed up.
As for the dashboard, I probably should clarify, it opens immediately, but on the first opening it takes 6 seconds and a lot of CPU work to calculate the new media counters.
On a second dashboard opening the counters are there immediately, but presumably they have been cached, and the 6 seconds CPU spike is still there in the background calculating new values.
I presume all the CPU work goes into database shenanigans. My data/jellyfin.db is 1.6 GB and I don't know if SQLite was ever meant to grow that large.
Maybe once Jellyfin supports PostgreSQL or another more optimized DB engine things will speed up.
As for the dashboard, I probably should clarify, it opens immediately, but on the first opening it takes 6 seconds and a lot of CPU work to calculate the new media counters.
On a second dashboard opening the counters are there immediately, but presumably they have been cached, and the 6 seconds CPU spike is still there in the background calculating new values.