• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

2 partitions for DV editing

Bfavre444

Senior member
I just got a 200GB drive for DV editing and I split it up into 2 partitions. I did this because I read somewhere that for DV editing (for Adobe Premiere), you should have 1 drive for storing captured AVIs and 1 drive for the preview files so exporting can read from 2 separate drives simultaneously, thus reducing stutters. The question here is about partitions: I know my 2 partitions "show up" as 2 drives, but do they "act" like 2 drives? The 2 "real" separate drives setup is best because it reads the captured AVIs from 1 drive and preview files from another drive simultaenously. Will 2 partitions on the same drive deliver the same performance?

Or will having 2 partitions basically serve no purpose, where it just performs just like 1 drive since there's only one read-head.

I hope that was easy to understand (it was a little hard to explain)

Thanks.
 
Or will having 2 partitions basically serve no purpose, where it just performs just like 1 drive since there's only one read-head.
Yep, that is correct since it is still on the same physical drive. You will need two actual drives to see a performance boost (RAID or otherwise).
 
Would creating 2 partitions actually decrease performance then? I mean, the other partition would be located at a different place on the drive than the first partition. So if the read-head is trying to read from one partition at one location and trying to read simultaneously from the other partition at that location, that would decrease performance I think?
 
Originally posted by: Bfavre444
Would creating 2 partitions actually decrease performance then? I mean, the other partition would be located at a different place on the drive than the first partition. So if the read-head is trying to read from one partition at one location and trying to read simultaneously from the other partition at that location, that would decrease performance I think?

Yeah, it probably would decrease performance slightly, as the read/write heads need to move from one half of the drive to the other, and back again.


Confused
 
Can't log in on this PC, no cookies, but something I forgot to add.

Having seperate partitions will reduce fragmentation of the files. Having a partition for your OS, a partition for temporary (often changing) work, and a final one for storage, will probably be the next best thing. If you do the editing on the same partition as the rest of the work, then the drive/partition will become fragmented a lot. Keeping everything seperate will reduce this happening, and may keep things a little faster 🙂


Confused
 
This is one big 200GB just for editing. So it only has AVI files, project files, sound files, graphic files. There's no other work for this drive nor an OS. So I take it one whole partition is best.

Thanks a lot Confused. 😉
 
Back
Top