Server Version#: 1.112.0.359-0d79a49f
Player Version#: N/A
If a client has a long movie paused, does the transcoder continue transcoding as long as it has space? I have a client which has a long file paused at (1 hr 30 out of 3 hr 30). The dashboard seems to show they have a buffer nearly until the end of the file. My server has around 16 GB RAM free normally, but the transcoder set to use RAM, and it seems like it might’ve filled up both RAM and swap.
Is this the cause, and if so, is there a way to limit the amount of transcoding space used per client?
What do you have written in under Settings > Transcoder > Transcoder default throttle buffer?
However many seconds you have there will be the transcoded buffer. I have 360 so it transcodes in 6 minute sections and near the end of that it will do the next section.
If you run linux and have the Transcoder temporary directory set to /dev/shm it will only have 8GB of RAM available if your 16GB is the total RAM you have for your computer.
Something to also consider is that the transcoder buffer also keeps the previously transcoded data. So it’s not just the look-ahead buffer you need to be concerned with.
The general rule is that you need to have sufficient space for all the media being transcoded, plus 100 MB for each file.
This is one reason why using RAM as the transcode buffer location is not always ideal. Why are you using RAM?
The buffer is set to 240, but I think it was something to do with the RAM management. I reduced the amount of RAM allocation on a bunch of VMs and haven’t run into that issue again. The machine used to sit at 80-85% RAM utilization, but now it sits at 54% and I haven’t run into that issue again even with clients pausing their playback for a long time.
I have it using RAM to reduce wear on the somewhat crappy QLC SSD.
This is what spinning disks are good for. Even a cheap external USB 3 hard drive would be sufficient in most cases.
