2023-10-09, 04:50 PM
(This post was last modified: 2023-10-09, 04:53 PM by Strangle7068. Edited 1 time in total.)
One other question, I did not know that trans-code file were written to disk, that's a lot of writes and I am a bit concerned about ssd write endurance here,
I have 2 ideas not sure if one or both of them would be silly or practical.
I have a scratch drive made from 2 1TB sas drives in R0 that I use as torrent cache, so that only completed files are written to the z2 pool in a nice orderly fassion, this scratch disk has plenty of room. its usually empty. would r0 spinning rust be fast enough for the transcode file?
If spinning rust is not fast enough I also have 1/4TB of EEC DDR3 ram at my disposal, ZFS is the big user here it uses it as cache space but never more than half of it, everything else barley makes the needle move, so I usually have 128GB or so of free ram, I could set up a ram drive for this trans-coding purpose? would 16Gb or 32Gb be sufficient?
I have 2 ideas not sure if one or both of them would be silly or practical.
I have a scratch drive made from 2 1TB sas drives in R0 that I use as torrent cache, so that only completed files are written to the z2 pool in a nice orderly fassion, this scratch disk has plenty of room. its usually empty. would r0 spinning rust be fast enough for the transcode file?
If spinning rust is not fast enough I also have 1/4TB of EEC DDR3 ram at my disposal, ZFS is the big user here it uses it as cache space but never more than half of it, everything else barley makes the needle move, so I usually have 128GB or so of free ram, I could set up a ram drive for this trans-coding purpose? would 16Gb or 32Gb be sufficient?