public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jonathan <jonathan@kc8onw.net>
To: cygwin@cygwin.com
Subject: Re: 1.7 ssh/rsync consuming all cpu on x64 Vista
Date: Mon, 29 Jun 2009 16:18:00 -0000	[thread overview]
Message-ID: <4A48E037.8060909@kc8onw.net> (raw)
In-Reply-To: <20090629100230.GE30864@calimero.vinschen.de>

On 6/29/2009 6:02 AM, Corinna Vinschen wrote:
> On Jun 26 22:02, Jonathan wrote:
>> I've noticed that most of the time when doing an rsync tranfser over ssh
>> from my laptop to my server both ssh and rsync will max out a processor
>> core each and the transfer rate, even on a gigabit LAN, is only about
>> 250KB/s.
>
> I'm getting a 6 Gigs/s rate using the latest Cygwin from CVS.  That's
> much better, though it's much worse than the 14 Gigs/s I get when using
> scp instead of rsync.
>
> Maybe you want to give the latest Cygwin snapshot from
> http://cygwin.com/snapshots/ a try.

I just need to replace the dll correct?  If so it didn't help CPU usage 
is still maxed out.  As noted in another email it only occurs when 
sending, receiving is normal.  What should I check next?

$ ldd /bin/rsync.exe
         ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x77570000)
         kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll 
(0x756a0000)
         cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
         ADVAPI32.DLL => /cygdrive/c/Windows/syswow64/ADVAPI32.DLL 
(0x770f0000)
         RPCRT4.dll => /cygdrive/c/Windows/syswow64/RPCRT4.dll (0x76d10000)
         Secur32.dll => /cygdrive/c/Windows/syswow64/Secur32.dll 
(0x75550000)
         cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x674c0000)
         cygpopt-0.dll => /usr/bin/cygpopt-0.dll (0x10000000)

$ ldd /bin/ssh.exe
         ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x77570000)
         kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll 
(0x756a0000)
         cygcrypto-0.9.8.dll => /usr/bin/cygcrypto-0.9.8.dll (0x6ba40000)
         cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000)
         ADVAPI32.DLL => /cygdrive/c/Windows/syswow64/ADVAPI32.DLL 
(0x770f0000)
         RPCRT4.dll => /cygdrive/c/Windows/syswow64/RPCRT4.dll (0x76d10000)
         Secur32.dll => /cygdrive/c/Windows/syswow64/Secur32.dll 
(0x75550000)
         cygz.dll => /usr/bin/cygz.dll (0x692c0000)

$ uname -a
CYGWIN_NT-6.0-WOW64 SAGER9262 1.7.0s(0.210/5/3) 20090628 15:28:41 i686 
Cygwin

Jonathan

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2009-06-29 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27  4:43 Jonathan
2009-06-29  5:51 ` Jonathan
2009-06-29  5:54   ` Jonathan
2009-06-29 14:24 ` Corinna Vinschen
2009-06-29 16:18   ` Jonathan [this message]
2009-06-29 17:48     ` Chris Sutcliffe
2009-06-29 18:03       ` Jonathan
2009-07-02 15:41         ` Jonathan
2009-07-02 16:35           ` Andy Koppe
2009-07-02 17:06             ` Vincent R.
2009-07-02 18:48               ` Larry Hall (Cygwin)
2009-09-04 18:06 ` scp consumes all CPU when sending data (was Re: 1.7 ssh/rsync consuming all cpu on x64 Vista) Jonathan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A48E037.8060909@kc8onw.net \
    --to=jonathan@kc8onw.net \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).