Windows 2003, Cygwin, and rsync

Aaron Morris aaronwmorris at gmail.com
Sat Jun 24 20:44:04 GMT 2006


On 6/23/06, John Oliver <joliver at john-oliver.net> wrote:
> On Wed, Jun 21, 2006 at 05:06:22PM +1000, Christian Hack wrote:
>> As for you speed issues. From a Dual Xeon 3.2GHz to a dual P3 1GHz ....
> I creted a ~250MB test file and was able to scp it between these NASes
> at ~40mb/s
>
> rsync still was transferring at about 12 mb/s over a direct 1Gb/s link.
>
> sent 665653991 bytes  received 78242 bytes  395210.59 bytes/sec total
> size is 62501572674  speedup is 93.88 rsync error: some files could not
> be transferred (code 23) at
> /home/lapo/packaging/tmp/rsync-2.6.6/main.c(791)
>
> real    31m47.484s
> user    1m49.609s
> sys     2m15.998s
>
> I am dealing with a lot of small files... about 50 GB of ~180,000
> someodd files.
>
> I'll check out that -W, but is there anything else that might improve
> this seemingly-pathetic performance?
>
> --
> ***********************************************************************
> * John Oliver                             http://www.john-oliver.net/ *
> *                                                                     *
> ***********************************************************************

While 12mb/s does seem rather slow, your problem is likely a
combination of cygwin and the slower machine.  Cygwin is, well, slower
than just running on a standard Unix/Linux platform and running it on
a slower machine will cripple the transfer even more.  I would suggest
taking SSH out of the equation and setup a rsync daemon; perhaps that
will speed things up.

Otherwise, if you look at the time savings rsync has given you, one
might not complain as much.  If you had transferred the 58GB using
straight scp, it would have taken ~3.3 hours, rsync did the same job
(net result, anyway) in 30 minutes.  That is very impressive.

-- 
Aaron W Morris (decep) <aaronwmorris at gmail.com>


More information about the rsync mailing list