Yesterday, 09:38 PM
I'm working through a preexisting library saving image assets locally at this time, and I had a question regarding how they are retrieved.
The media files are on conventional spinning hard drives, but the Jellyfin server is installed on a NVME drive. If I save the image assets (posters, backdrops. etc) locally the files are being saved with the media they go with. Are these copies accessed every time a client needs to display them for a library or preplay screen, or does Jellyfin create a cache in its own server install location of the images?
I like the idea of saving the images locally in case I need to rebuild a server, but I don't want to reduce responsiveness in browsing because of the images being retrieved from the slow hard drives instead of the NVME.
The media files are on conventional spinning hard drives, but the Jellyfin server is installed on a NVME drive. If I save the image assets (posters, backdrops. etc) locally the files are being saved with the media they go with. Are these copies accessed every time a client needs to display them for a library or preplay screen, or does Jellyfin create a cache in its own server install location of the images?
I like the idea of saving the images locally in case I need to rebuild a server, but I don't want to reduce responsiveness in browsing because of the images being retrieved from the slow hard drives instead of the NVME.