I have a IBM x3850 X5 running 4 E7-8870 and 64 gigs of RAM with 10 terrabytes of internal HDD storage. I have installed UnRAID version 6.5.0 and have Plex running in Docker. and all i run is plex and after 7 (2 trans-coded 5 direct ) streams it (PMS) freaks out and says “Not enough CPU to trans-code” yet im running less then 10% CPU and only 1.3G of ram…HELP
Whats sort of file is it?
VC-1 can only utilize 1 core for transcoding
and plex need ca 2000 passmark points per transcoding stream, your processor have 700 as singeltread score.
Using the web interface, check Settings -> Server -> Transcoder -> Maximum simultaneous video transcode. You likely have it set to 2.
no its unlimited

@Gothix said:
what is VC-1? and how do i find out if my media is VC-1? isnt that a WMP format? 99%% of my video is MP4 or MKV i need to be able to use all my power lol
![]()
VC-1 is a fileformat just like MP4 or in this case H264.
MKV is a container that holds the different fileformats.
Take a look at Spaceinvaders (Gridrunner @limetech forum) YT videos in how too tune an unRaid-Server
and se if that makes any differens.
He makes great tutorial videos of how to get the most out of unRaid.
Thank you, I’ll do that now.
@Mattias_Eriksson said:
@Gothix said:
Take a look at Spaceinvaders (Gridrunner @limetech forum) YT videos in how too tune an unRaid-Server
and se if that makes any differens.
He makes great tutorial videos of how to get the most out of unRaid.
that did it 12* (11 had to kill 1 to take the pic) full trans streams and 40% before the drives couldn’t keep up!!!
thank you all!!

@Gothix said:
that did it 12* (11 had to kill 1 to take the pic) full trans streams and 40% before the drives couldn’t keep up.
Are you running Plex of an SSD, if not you will get a performance gain in having the /transcode folder on an SSD.
Search for Byte my Bits on YT, i think he has a video comparison between SSD & HDDs transcoding.
@Mattias_Eriksson said:
@Gothix said:
that did it 12* (11 had to kill 1 to take the pic) full trans streams and 40% before the drives couldn’t keep up.
Are you running Plex of an SSD, if not you will get a performance gain in having the /transcode folder on an SSD.
Search for Byte my Bits on YT, i think he has a video comparison between SSD & HDDs transcoding.
I have watched it many times and the reality is is trans coding on a SSD will kill the SSD and I’m not looking to kill hardware… tho making a Virtual disk that uses ram is the way to go but I am still trying to figure out how to make a ram disk in unRAID.
Thank you for the help I couldn’t have done any of this without you guys!!!
Per the real performance issue, where exactly are you seeing this message about not enough CPU? It is in the server logs around the transcode process? You may want to see if you are restricting the CPU usage of your docker container; it is possible that the container is not being allowed to use your full CPU resources.
VC-1 is a fileformat just like MP4 or in this case H264.
MKV is a container that holds the different fileformats.
So much wrong here: VC-1 and H.264 are codecs, not file formats and the data itself is often called a bitstream. MP4 is a container (file format). MKV is a container that holds codec bitstreams, not file formats.
I have watched it many times and the reality is is trans coding on a SSD will kill the SSD and I’m not looking to kill hardware… tho making a Virtual disk that uses ram is the way to go but I am still trying to figure out how to make a ram disk in unRAID.
The only legitimate reason I’ve ever seen to suggest putting the transcode temp on a RAM disk is to prevent aging of an SSD. If you can put it on a spinning disk, this will be perfectly fine. Some suggest that it be put in a RAM disk for performance reasons, but this just demonstrates a fundamental misunderstanding of how operating systems manage their RAM and in particular their disk cache. So long as you aren’t saturating the write abilities of your spinning disk, it’ll serve perfectly fine as a transcode cache and the segments themselves will be served to the clients out of the disk cache rather than being actually read from the disk. When you are using a RAM disk, that RAM in inaccessible for other purposes so a client an hour into watching a movie will still have a segment made and served to the client an hour ago still consuming RAM. Without using a RAM disk, the OS then has the freedom to flush old data out of the disk cache to make room for other RAM uses (you are highly unlikely to need a segment again that was written to the disk an hour ago, but if you do, it can be read from the disk). In short, use a spinning disk, not a RAM disk, for your transcode temp.

