Question about Transcoder temporary directory

Server Version#: 1.41.5.9522
Player Version#: n/a

I’m trying to improve the transcoding performance of my server and one suggestion I saw was to move the Transcoder temporary directory to a RAM disk. I’ve done that, but I’m curious what will happen in the event that my RAM disk fills up? I’m hoping that I can do something like sets a Transcoder temporary PATH (using a semi-colon between folders, just like the PATH envar) so that Plex can keep trying to work even if the RAM disk fills up.

I set it to 16GB and most of my media files are <= 4GB, so with my very few users I think I should be OK, but it would be nice to know what’s going to happen and if the server has any sort of contingency plan should it run out of transcode space (which would only make sense.) If the server just gives up, I’d at least like to learn what the errors I’ll be hearing about will say – and I hope they aren’t as non-specific as “server not powerful enough” when a third user tries to watch a show on a 3.4GHz, Core i7-3770 with 4 cores (8 logical) and 64GB of RAM – especially when the CPU is at about 15%, so there’s power to spare … at least that I can see.

Hi… When the temp transcoder location is almost full, Plex will start to automatically delete the oldest chunks to free up space, so you should be OK.

Although if you have got 64 GB of RAM in the machine and not much else running on it, I’d suggest setting the RAM disk to 32 GB, just because you can :+1:

1 Like

Thanks for the info. Sadly, I was wrong about the total memory, it only has 32GB total – my machine at work has 64GB and my addled old brain mixed 'em up. Still, I might be able to raise it to 20 or 24GB, since the system seems to be using less than 8GB when running normally. It is dedicated to being a Plex server.

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.