public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jordan Geoghegan <jgeoghegan60@gmail.com>
To: L A Walsh <cygwin@tlinx.org>
Cc: cygwin@cygwin.com
Subject: Re: Network Performance?
Date: Mon, 09 Apr 2018 18:30:00 -0000	[thread overview]
Message-ID: <04ef0912-46d6-3332-a3e2-0436e30d1452@gmail.com> (raw)
In-Reply-To: <5ACAA0E6.5040504@tlinx.org>

Thanks for testing that for me! I had feared I was having filesytem 
speed issues as seen in WSL, but alas I was wrong. It turns out my issue 
with network performance bottnecks is due to the TCP window size not 
adjusting. Looking at the debug output of ssh, it seems the window size 
adjusts aren't being performed. Strangely enough, when I grabbed a fresh 
machine to test Cygwin on, I am able to get near wire speeds. Very strange.


On 04/08/18 16:08, L A Walsh wrote:
> Jordan Geoghegan wrote:
>> Thanks for the info. Would you be able to test file performance over 
>> the network? If you could just try copying a ~1GB file or what have 
>> you via sftp or rsync with actual writes to disk, I would be very 
>> interested to see how the numbers change.
> ---
>     Here is scp and rsync, using a tar, and a 1g file filled
> with zeros.   Note, my env RSYNC_RSH=ssh
>
>> time scp default-nlaw.tar.7z ishtar:/tmp 
> default-nlaw.tar.7z                           100%   62MB 83.1MB/s   
> 00:00    0.91sec 0.04usr 0.01sys (6.65% cpu)
>> ssh ishtar rm /tmp/default-nlaw.tar.7z
>> time rsync -v default-nlaw.tar.7z ishtar:/tmp/
> default-nlaw.tar.7z
> sent 64,588,267 bytes  received 35 bytes  43,058,868.00 bytes/sec
> total size is 64,572,413  speedup is 1.00
> 0.73sec 0.37usr 0.17sys (74.32% cpu)
> time scp /tmp/1g ishtar:/tmp/ 
> 1g                                            100% 1014MB 72.3MB/s   
> 00:14    15.00sec 0.04usr 0.07sys (0.81% cpu)
>> time rsync -v /tmp/1g ishtar:/tmp/
> 1g
> sent 1,063,515,721 bytes  received 35 bytes  125,119,500.71 bytes/sec
> total size is 1,063,256,064  speedup is 1.00
> 7.57sec 5.95usr 3.40sys (123.54% cpu)
>
>> uname -a
> CYGWIN_NT-6.1 Athenae 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin
>
>
> I generally don't use them to transfer files over a closed
> subnet as the performance is sub-optimal.
>
> -- 
> 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
>


--
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:[~2018-04-09 18:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 22:40 SSH/SFTP " Jordan Geoghegan
2018-03-24  0:57 ` L A Walsh
2018-03-25 10:24   ` L A Walsh
2018-03-27  3:54     ` Jordan Geoghegan
2018-04-08 23:08       ` L A Walsh
2018-04-09 18:30         ` Jordan Geoghegan [this message]
     [not found] ` <d1353aaf-271a-ba2f-7de0-80ca15b18e01@cs.umass.edu>
2018-03-24  2:06   ` SSH/SFTP " Jordan Geoghegan
2018-03-24  5:07     ` Eliot Moss

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=04ef0912-46d6-3332-a3e2-0436e30d1452@gmail.com \
    --to=jgeoghegan60@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@tlinx.org \
    /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).