2024-04-17, 11:23 PM
Not sure if my expectations are flawed or not, but I have Jellyfin setup in docker with the cache, metadata, and config folders all setup to use a NVMe drive, while all the media is on the normal old fashioned spinning HDD array. What I'm hoping to achieve with this configuration is to have it only access the NVMe drive when browsing the library, both for the speed benefit and to reduce the time the HDD drives are spinning. The only time the HDD would be accessed is when media is selected and begins playing, allowing the drives to spin down for most of the day. However, when browsing there's a fairly long delay when displaying each new page of thumbnails, and I can hear the hard drive chattering away. Effectively this means any time anybody even glances at Jellyfin on their phone or whatever the hard drives have to jump into action, which as I understand things just shouldn't be the case.
The strange part is the cache, metadata, and config folders are all plainly visible on the NVMe drive, and no equivalent folders exist on the HDD, so what exactly would Jellyfin be reading from the media drive when simply browsing libraries? And, more importantly, is there any way of stopping it from doing that?
The strange part is the cache, metadata, and config folders are all plainly visible on the NVMe drive, and no equivalent folders exist on the HDD, so what exactly would Jellyfin be reading from the media drive when simply browsing libraries? And, more importantly, is there any way of stopping it from doing that?