Image asset caching.

[SeaFox]

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.

[crobibero]

If the client requests a resized image the resized image is cached. I don’t believe the original image is cached

The client should be caching the image so it doesn’t need to be pulled every time

[SeaFox]

Okay, I guess I will keep an eye on this and see how it goes. I have a TV with a Fire Stick in the same room as the server and could hear the disks seeking and see activity lights flashing exactly at moments I was scrolling in a library view so it seemed to be pulling the poster images directly from the slower spinning storage. Maybe that will cease after awhile once I have finished with this resaving operation on all titles and used it for a bit.

[Bladefin]

Interesting my video files are also on a HDD and Jellyfin on a SSD when I had posters etc.. on the HDD the clients were noticeable slower to show posters etc..

I never noticed a increase in loading after a month.