2025-05-27, 08:53 PM
(This post was last modified: 2025-05-27, 08:57 PM by toytown. Edited 2 times in total.)
Hi
I really think the cache directory (not transcode directory) needs a re-work, i deleted it about 2 days ago as it was using around 30GB. It's currently back to 14GB and rising.
So i decided to look into what it actually contains. I found that in the resized-images folder, i have the backdrop image in WEBP format (2160p) for a film using 12MB, yet the original image from my /config/metadata/library/ is in JPG format (2160p) and only using 1.9MB of data (6x less). This is repeated tons of times for all different films. Why are these images even created? Why not just serve them direct from the original source, as they will be be of higher quality and faster to push over the network, with the addition of not using any extra diskspace.
If the reason is to speed up access times when jellyfin itself is hosted on a spinning HDD, then could there be an option to remove the cache when jellyfin is hosted on SSD/NVMe drives.
Thanks for listening
I really think the cache directory (not transcode directory) needs a re-work, i deleted it about 2 days ago as it was using around 30GB. It's currently back to 14GB and rising.
So i decided to look into what it actually contains. I found that in the resized-images folder, i have the backdrop image in WEBP format (2160p) for a film using 12MB, yet the original image from my /config/metadata/library/ is in JPG format (2160p) and only using 1.9MB of data (6x less). This is repeated tons of times for all different films. Why are these images even created? Why not just serve them direct from the original source, as they will be be of higher quality and faster to push over the network, with the addition of not using any extra diskspace.
If the reason is to speed up access times when jellyfin itself is hosted on a spinning HDD, then could there be an option to remove the cache when jellyfin is hosted on SSD/NVMe drives.
Thanks for listening