3 ms·
Or it could be a boon for video/audio/graphics types. I’m used to setting up my spinning rust arrays with 64k block sizes. Continuous reads from large files vs
by dylan604 2y ago
Or it could be a boon for video/audio/graphics types. I’m used to setting up my spinning rust arrays with 64k block sizes. Continuous reads from large files vs lots of tiny files is something that tripped up a lot of storage vendors trying to break into the media world.
- bufferoverflow 2y agoIt's very expensive. Gen5 SSDs are around $100/TB. Hard drives are $16/TB. It makes sense to have a small fast SSD for editing, but HDDs for mass-storage. And with video you usually want redundancy, storage gets expensive fast.
- dylan604 2y agoAnd with any data you usually want redundancy, FTFY But I know what you meant. I used to have systems built with multiple small arrays where the original sources were in RAID-5 (pre-raid6). The software would read from that array and write to a RAID0 array as these files were only ephemeral. The software would then read from that RAID0 and write to a second RAID0 to avoid reading/writing to the same volume. This was all before SSDs. For the lulz, I would love to see how that workflow would perform with NVMe storage. At the time of using these systems, spinning rust was not $16/TB and was probably closer to the $100/TB. I still remember $1k/GB in the early 90s
- bufferoverflow 2y agoAt the time you didn't have 8K or RAW videos or 200-megapixel photos. There's never enough storage.
- dylan604 2y agoWhile not 8k, it was 4K-5k and definitely RAW. While never enough storage, we have achieved a point where disk I/O is not a bottle neck. It used to take a raid0 7 disk stripe to record SD video only while the audio was written to a separate drive. The fact we can record 8k RAW with audio on a single drive the size of a stick of RAM is crazy to compare. Smaller faster cheaper.