Does Transcoding benefit from the Temporary Directory being on an SSD?

Server Version#: 1.18.2.2058 on FreeNAS 11.2-U7
ASRock E3C226D2I, Intel Core i3-4370, 16 GB ECC RAM, 6x8 TB WD80EZAZ RAID-Z2

I recently switched from my Boot Volume being two mirrored USB sticks, to two mirrored Kingston A400 120 GB SSDs.

Furthermore I’ve added a Kingston UV500 240 GB SSD to hold my FreeNAS iocage/jails, including Plex Media Server and the PMS Database. The media itself still sits on the 6x8 TB RAID.

My question now is: Does the transcoding benefit from the SSDs (in terms of snappiness, quicker playback start) or is the CPU performance the actual bottleneck?

Also: What’s the default location of the Transcoding Temporary Directory? The FAQs say „By default, the temporary files are stored on the OS boot disk.“ So, that would be the Boot Volume of my FreeNAS in my case? Or the SSD on which the iocage sits (inside which PlexMS runs)?

Default location is where PMS is installed. If that is an SSD no point setting another location. I have PMS on NVME drive in a qnap NAS. I cannot see any speed difference to a sata SSD.

See @ NVME wear and tear like normal SSDs with lots of read/writes?

I think there is some confusion here, my question is not NVMe/PCIe SSD vs. SATA SSD, it’s SSD vs. HDD RAID.

So, reviously I was booting the FreeNAS from USB sticks, but Plex ran entirely in an iocage/jail on the HDD RAID. Now am booting the FreeNAS from one SSD, and Plex with its index/database runs in an iocage/jail on a separate SSD, while the media files remain on the HDD RAID.

In other words: Previously the transcoding temp directory sat on the HDD RAID, now it sits on the SSD.

And my question is (wear of the SSD aside): Does the transcoding process benefit from the temp directory on the SSD (instead of the HDD RAID?

Did you read my reply?

If the temp is now on an SSD compared to formally being on your Raid HDD the answer is yes.

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