2024-11-22, 04:32 PM
(2024-11-22, 04:06 PM)TheDreadPirate Wrote: If it was busy generating trick plays or chapter image extraction, those usually may appear in the dashboard as an active job. But your log would show what activity is going on. Regardless, the disk IO for a database easily saturates a HDD.
What you can do in the meantime is to limit the number of library scan threads.
Dashboard > General. Set both "Parallel library scan tasks limit" and "Parallel image encoding limit" to 1.
If you intend to keep the NAS, I'd choose a mini PC with an N100 over a 5700U. The media engine in the N100 is MUCH better than the 5700U.
If you intend to build a proper server, including having storage be locally attached, we'd need a budget and intended usage to give more specific recommendations.
I came here to report exactly this.
I removed all the libraries, and IO was still high. I had tried changing the parallel setting right there, but it wouldn't let me. I restarted jellyfin, and IO was still high and I couldn't access jellyfin at all. I uninstalled deleting all app data to start fresh. The first thing I did was to set parallel to 1. Adding the first library and IO is high, but jellyfin remains responsive and the scan is happening quickly.
What I think happened is the same thing you are pointing out. This synology is a 4-core, so jellyfin might have been trying 3 or 4 parallel scans. It also wasn't able to control them so even when it tried to stop, the scan sub-processes were still running in the background. Restarting jellyfin was also restarting those scans. Even when I had tried to change the configuration to run nightly, it was still jammed from previous attempts.
Also, thanks for the tip on the N100. I had heard the N100 had a great media encoder, but it's good to know the comparison to the 5700U.