Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <009701c280a7$7c1cef40$010a10ac@bluesguitar.org>
From: "Matthew Smith" <matts AT bluesguitar DOT org>
To: "Cygwin" <cygwin AT sources DOT redhat DOT com>
Subject: Slow rsync
Date: Thu, 31 Oct 2002 00:33:54 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Note-from-DJ: This may be spam

Guys:

    I've been using rsync to keep a CVS repository up to date.  My main cvs
repository/rsync server is a Redhat 7.3 box.  I have the following alias set
up on my cygwin side:

alias getcvs='rsync -avuz -e ssh --exclude-from="/home/matts/.rsync.ignore"
linux:cvs .'

When running this rsync command from a linux client, the "receiving file
list ..." portion of the sync takes less than 1 second to complete.  When
running the same rsync command from the latest cygwin release on a Windows
XP box, it takes > 30 minutes for the "receiving file list ..." portion to
complete.  Now I understand that Cygwin is inherently slower, but this seems
more like a bug to me.  I did note that the task manager showed the
associated ssh process eating up 99% of the cpu during this 30 minute
period. Has anyone else seen this behavior?
    For the record, I checked the FAQ before posting, and didn't see
anything relevant to this question.  I also made sure to turn OFF virus
protection, and I made sure I didn't have multiple copies of cygwin1.dll
floating around. I also tried the hacked rsync.exe referenced here:

http://sources.redhat.com/ml/cygwin/2002-10/msg00296.html

Which also didn't work for me.  I tried the latest cygwin snapshot
(10/30/02), with no luck. Please also note that I have the CYGWIN environ
variable set to "nontsec".

thanks for any insight,
-Matt Smith



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/