Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Optimal cluster/Allocation unit size for formatting new media+ non-identical r3d size

Grayson Fahrner

Active member
Joined
Jan 29, 2018
Messages
43
Reaction score
0
Points
6
Location
Manhattan
As Red shooters our files are huge and therefore candidates for increasing allocation unit sizes on hard drives for theoretical "performance" gains.

BUT
Increasing block size on a hard drive means not keeping many other smaller files on those drives so as not to hog precious storage, a downside which might be small but is not theoretical.

1) Does increasing the block size from 4096-->64K-->256K and beyond on SSD/NVME systems actually do anything for storing/copying/editing .r3d files?

2) When copying over files from one hard drive to another, is anyone else bothered by the non-identical file sizes presented on both media due to differences in cluster size? I hate painstakingly copying footage to backup only to see different numbers show up, as I have had instances of non-identical file sizes revealing truncated footage once or twice.

3) Is there a benefit to keeping all allocation cluster units identical across all media? I use MAC for ingest in the field but edit on a PC and I really like to see file sizes nearly identical across the entire ingest/copy/edit media units.

4) Any other tips on formatting HDDs/SSDs/NVMEs for maximum performance? I'm a little confused on stripe size/device block size/partition alignment considerations as well.
 
Back
Top