OK, first of all, I don't know how you're configuring DVDShrink, but if the operations you're talking about are taking 41 seconds vs. 1 minute and 10 seconds, you're not doing any encoding. You're simply copying data. Transcoding a DVD with DVDShrink takes at least several minutes for a 2 hour movie, and that's with the fastest Core2 Duos available. Doing full reencoding with something like CinemaCraft Encoder and DVD Rebuilder takes even longer.
If you were actually encoding/transcoding, the hard drives wouldn't matter at all, since the bottleneck in such operations is not the hard drives, but the processor's speed and power.
Second, when doing DVD operations that involve copying a lot of data back and forth (i.e. multiplexing .m2v & .ac3 streams into .vob files during authoring, or making an .iso file out of a set of .vobs & .ifos), you will have much better throughput and performance by placing the source data on one hard drive and putting the destination file or folder on another hard drive. What you're doing in your setup is copying data from one folder to another folder on the same volume of the RAID 0, which is doing massive seeks back and forth to read some data, then write some data. By splitting the task with a single drive doing all the reading and a second drive doing all the writing, the overhead for seeking goes to nothing, and you can realize data transfer rates near the published benchmarks for STR.
The reason the Raptors are not performing as well as the 1TB drives here is because of the seek distances. The Raptors have small data capacity. To go from the beginning of the source files to the beginning of the target files when going back & forth for reading/writing, the Raptors seek a lot farther (more tracks) than the 1TB drives do. So even though the Raptors head movement is faster, it's also farther, and it loses time compared to the 1TB drives. Of course, if you configure the system like I stated, they won't be seeking back & forth at all.
Third, because copying data like this is a task that depends on STR and not access time (when configured for split drive operation like I said), and because the amount of data you're dealing with is in the GB range (DVDs), the WD 1TB drives are a far better fit for this application than the Raptors are.
I have a machine set up for reencoding DVDs, and I have it configured as follows:
- WD Raptor 74ADFD for C: drive (Windows & applications).
- Seagate 500GB for D: drive
- Another Seagate 500GB for E: drive
My process goes like this:
- Rip my legally purchased and owned DVD to D:
- Re-author with DVD Remake Pro, output to E:
- Re-encode with CinemaCraft Encoder Basic and DVD Rebuilder to E:, using D: for intermediate files
- Burn my backup/working disc from E: to DVD
- Carefully store original out of reach of the kids
By going back and forth between drives like this, I get maximum throughput on the operations that involve just copying data (the DVD Remake Pro output operation, and the DVD Rebuilder rebuild operation). No RAID is involved.