Temporary transcoding files - space needed?

[Dodgee 0]

I'm not sure how easy this is to answer as it's probably quite variable, but can anyone tell me how much disk space is needed in the temporary transcoding path?

 

For example let's say one large MKV file of about 20GB is being played and needs to be transcoded.  Would I need a full 20GB free on the disk where the path is located to be able to watch the whole movie?  Would I need less because only a portion of the file is buffered at any one time?  Or would I actually need more because an additional file is created when it's transcoded or something?

 

Sorry, a bit vague I know.  Any further info about how the transcoding process works would be great!

[Luke 42083]

I think the best rule of thumb would be to allocate the same amount of size as the original video. It is very unlikely that a transcode would ever reach the same amount but I think that is a safe recommendation.

 

Then multiple that by the number of simultaneous transcoding sessions you intend for your server to support.

[Dodgee 0]

Perfect, thanks

[nvader2000 12]

I have Emby install on my Synology DS3615sx primary boot drive which happens to be SSD. I have two other 512Gb SSDs (RAID1) installed as well that I was considering on using for cache. Do I gain anything by moving the transcoding cache directory to these over the default directory? I think moving would mitigate the amount of I/O on the boot drive thus increased performance and that my two 512gb SSds are in a RAID1 I would suspect an additional performance increase there as well.

 

I am correct in my thinking?

[legallink 187]

I think your performance increase, if any, will be minimal. That being said, as a general rule of thumb I would take any I/o intensive tasks and move them off the boot drive if you have the option. The amount of I/O here isn't enough to task an SSD unless you have a lot of streams going st the same time.