2024-12-31, 04:38 AM
(This post was last modified: 2024-12-31, 04:36 PM by SmellyJellyBelly. Edited 3 times in total.)
. delete
|
Yesterday, 07:24 AM
I have a large library of 4K HDR content on a system with 64GB of DDR5 and was using a tmpfs RAMDisk for a long time until I started running into problems when storing uncompressed content which filled up the transcode cache.
Now I just leave the transcode directory as default which is on a 1TB PCI-E Gen4 Nvme. No issues since and like others have said, the write endurance is massive.
Yesterday, 01:52 PM
(This post was last modified: Yesterday, 01:53 PM by TheDreadPirate. Edited 1 time in total.)
FWIW, enabling "Delete segments" and "Throttle Transcoding" plus tightening how far ahead transcoding is allowed and when segments are deleted really helps with controlling RAM disk usage for transcodes.
Jellyfin 10.10.3 (Docker)
Ubuntu 24.04 LTS Intel i3 12100 Intel Arc A380 OS drive - SK Hynix P41 1TB Storage 3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library) ![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github){kind=icon}
|
|
|
|
|
