Also, keep in mind that 1TB of small files takes longer to copy than a single 1TB file.
------------------
Jeff Hedberg
Union Editorial
575 Broadway,6th floor
New York, NY 10012
On Dec 16, 2016, at 12:51 AM, Michael Brockington mbrock321@gmail.com [Avid-L2] <Avid-L2@yahoogroups.com> wrote:I don't think Shotput Pro's copy time estimates are all that accurate, at least with the older version on Macs.
I did some benchmarking with the program in 2014. Copy without checksum took about the same time as a desktop file copy (so the limiting factor was the speed of the disks.) Adding MD5 checksums doubled the copy time, as others have reported.
A notable advantage to Shotput Pro is that adding additional copy destinations doesn't increase the copy time. If you have 2 target drives set as destinations, then 2 copies should take about the same length of time as doing a single copy. That's assuming you're using a fast interface like USB3 or thunderbolt. It reads the source file only once and does the writes in parallel, presumably.
So if you have to make 2 copies anyway, you can turn on the MD5 checksums in Shotput Pro, and it should take about as long as doing 2 copies sequentially in the finder without any checksum.
I used 128 GB of test data. It took 19 minutes with no checksum, 38 minutes with MD5 checksum, copying to an empty 2TB Lacie rugged drive (only 5400 RPM.)
Cheers,
--Michael Brockington
After my recent thread regarding copying software the offered MD5 checksum and a log Shotput Pro was suggested by several. We purchased it and on a MacPro Tower with a 4TB Graid source drive and a 20TB Graid target drive, both connected to a usb 3 card for approximately 1 TB of Panasonic Varicam 35 4096x2160 avc-intra media the computer said 24 hours to copy. After a few restarts they moved the software to a different MacPro Tower. Both Macs are mid 2010 modified to 12 core running OS 10.9.5. The second computer said 12 hours but both seemed to stall in the process.We are not familiar with this process but I have been told by a more experienced friend the MD5 is CPU intensive. The CPU are 12 core 3.33Ghz. I can't believe that DITs in the field are taking 12 hours to copy drives to comply with the checksum MD5 log that is being required by the network. Most of our shoots have more like 2TB of camera media. I know there are options to just check file size and other check sum types that aren't as time consuming but the network specifically requests MD5. Is the large size of video files making the MD5 process much longer than it would be with more typical data that IT folks would deal with.What should 1TB of camera media take to copy on the above listed drives with an MD5 checksum.Also due to our OS they are running ShotPut Pro 5.x not 6 as that requires OS 10.10 which won't work with the rest of our infrastructure.John Moore Barking Trout Productions Studio City, CA bigfish@pacbell.net
Posted by: Jeff Hedberg <jeff@unioneditorial.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (16) |
No comments:
Post a Comment