Dustin Cross
Well-known member
- Joined
- Mar 6, 2007
- Messages
- 1,240
- Reaction score
- 0
- Points
- 0
- Location
- Austin, Texas
- Website
- www.sandust.com
Nick,
Get the Atto H680. If you need three now, having eight available doesn't hurt. Atto makes a one SAS port (4 esata) card (H644), but the price is about the same as the H680. Get the H680.
There are a couple ways I save time with a fast raid.
First lets look at how R3Ddata manager and shotput work. They do one read and multiple writes. They can't read again until the write is finished. So they can only copy as fast as the slowest destination drive. If you have two drives that work at light speed and one slow old USB drive the entire copy will be at the speed of the slow old USB drive. If you have a slow source, like Red station connected via USB and you are writing to multiple super fast destination drives, you will be limited by the bandwidth of the USB source.
I wrote my own little app (posted on Reduser) that copies to the fast raid first and from the fast raid to all other drives. It checksums the source media and each of the destinations as soon as the copy is done and compares all the checksums to the source. The first place this speeds things up is as soon as the card is copied to the raid and checksumed, I can pull the card and send it back to camera. The card just has to get through one superfast copy/checksum and it is ready to go back to set. Since my raid is raid 6 I have lots of protection for that one copy. Raid 5 works great, but gets really scary when you loose a drive on set and you have no protection until the raid rebuilds several hours later.
Next my script is general faster than RDM or Shotput because one semi performing destination drive really kills them. And as drives fill up they slow down. With three fast drives and plenty of bus, RDM is slightly faster and I have not tested the new Shotput, but the old shotput was stupid slow. My app gets a speed advantage because while it is waiting for the slow drive to finish, it can start the checksum process on the rest of the drives. RDM has to wait for all the copies to finish before it starts checksum. So two drives can be sitting idle while waiting on the third drive to catch up so they can move to the next step.
Checksums can really be slowed down by a slow or shared bus, because multiple drives are being read at the same time. If each drive can read at 120MB/s, but all three are on a 100MB/s firewire bus, they will only read at 33MB/s each while reading at the same time. That is only a 20% performance hit for a single drive, but about a 65% performance on parallel operations.
Adding a fast raid to RDM or Shotput won't speed up your process. It will give you fast storage to work from without impacting downloads.
Hopefully that makes sense.
Dusty
Get the Atto H680. If you need three now, having eight available doesn't hurt. Atto makes a one SAS port (4 esata) card (H644), but the price is about the same as the H680. Get the H680.
There are a couple ways I save time with a fast raid.
First lets look at how R3Ddata manager and shotput work. They do one read and multiple writes. They can't read again until the write is finished. So they can only copy as fast as the slowest destination drive. If you have two drives that work at light speed and one slow old USB drive the entire copy will be at the speed of the slow old USB drive. If you have a slow source, like Red station connected via USB and you are writing to multiple super fast destination drives, you will be limited by the bandwidth of the USB source.
I wrote my own little app (posted on Reduser) that copies to the fast raid first and from the fast raid to all other drives. It checksums the source media and each of the destinations as soon as the copy is done and compares all the checksums to the source. The first place this speeds things up is as soon as the card is copied to the raid and checksumed, I can pull the card and send it back to camera. The card just has to get through one superfast copy/checksum and it is ready to go back to set. Since my raid is raid 6 I have lots of protection for that one copy. Raid 5 works great, but gets really scary when you loose a drive on set and you have no protection until the raid rebuilds several hours later.
Next my script is general faster than RDM or Shotput because one semi performing destination drive really kills them. And as drives fill up they slow down. With three fast drives and plenty of bus, RDM is slightly faster and I have not tested the new Shotput, but the old shotput was stupid slow. My app gets a speed advantage because while it is waiting for the slow drive to finish, it can start the checksum process on the rest of the drives. RDM has to wait for all the copies to finish before it starts checksum. So two drives can be sitting idle while waiting on the third drive to catch up so they can move to the next step.
Checksums can really be slowed down by a slow or shared bus, because multiple drives are being read at the same time. If each drive can read at 120MB/s, but all three are on a 100MB/s firewire bus, they will only read at 33MB/s each while reading at the same time. That is only a 20% performance hit for a single drive, but about a 65% performance on parallel operations.
Adding a fast raid to RDM or Shotput won't speed up your process. It will give you fast storage to work from without impacting downloads.
Hopefully that makes sense.
Dusty