That makes sense as its essentially a software raid.
It has nothing to do with being software raid.
Harddrives (the big spinny things) themselves have sucky read+write performance due to their very nature.
There is no big advantages to creating a ramdisk. Plex is designed to just store the buffer on disk.
Well, as I explained before there are advantages. If they would be big or not, really depends on your setup and requirements. It isn't for us to judge.
As a ramdisk is just blockstorage for all we care, plex would be perfectly happy with it. It doesn't require persistent blockstorage according to the documentation.
I'm very new to this 1-2 weeks max I no idea how to interpret what you said into an actionable sequence that makes sense.
I that case you might wanna ask yourself why you are messing with advanced tweaks that aren't required?
TLDR:
iocage fstab -a "$1" tmpfs /tmp_transcode tmpfs rw,size="${plex_ramdisk}",mode=1777 0 0
P.S what I have done exactly is clearly laid out above :)
I know, and as I said it's a stupid way of doing it. Don't build a pool on a ramdisk. period.
I can only go by what the results are, doing this solved my problem.
Maybe you should look into the cause of the problem and not pick one solution before finding the cause?
Something is clearly wrong with your install.
The reason transcoding would cause some jitter in some setups is them being CPU bound (the CPU needs to transcode x minutes of buffer from the new scroll position), it shouldn't be harddrive bound. If your harddrives can't handle the writes of a single transcode you have a bigger problem under the hood than just plex being slow.