From: Jordan Geoghegan <jgeoghegan60@gmail.com>
To: L A Walsh <cygwin@tlinx.org>, cygwin@cygwin.com
Subject: Re: Network Performance?
Date: Tue, 27 Mar 2018 03:54:00 -0000 [thread overview]
Message-ID: <8794ec10-dcee-4ad6-bfe6-3c8c108ca5f6@gmail.com> (raw)
In-Reply-To: <5AB6E770.8020603@tlinx.org>
On 03/24/18 17:04, L A Walsh wrote:
> L A Walsh wrote:
>> Jordan Geoghegan wrote:
>>> Has anyone ever successfully transferred 150Mbps or more over the
>>> network using scp/sftp/rsync etc on Cygwin?
>> ----
> What is more important? testing cygwin's scp/sftp/rsync, or using 'ssh'
> or running under cygwin, or transferring the file to a local backup
> server from a windows
> client as fast as possible?
What is most important is getting reasonable performance when moving
data via ssh, be it sftp, rsync or some other sort of data tunnelling
via ssh. I need to pull backups from a Windows box, and am only able to
get ~8MB/s from it. All my other machines can saturate the line, even
this Windows box when it isn't using Cygwin. I will be testing WSL
(Windows Subsytem for Linux) to see how its "native" rsync fares in
comparison.
>
> Some test notes below(been benching my win<->server speeds since Win98
> days)...
>
>> Using bs=16.0M, count=64, iosize=1.0G
>> R:1073741824 bytes (1.0GB) copied, 1.66724 s, 614MB/s
>> W:1073741824 bytes (1.0GB) copied, 3.48363 s, 294MB/s
> ---
>
> The above test only tests transfer speed -- not file i/o --
> it uses /dev/zero for a source and /dev/null for a target.
> For write, I used cygwin's 'dd' with if=/dev/zero and of=/h/null.
> For read, I used if=/h/zero and of=/dev/null.
>
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.
Jordan Geoghegan
--
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
next prev parent reply other threads:[~2018-03-26 17:49 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 [this message]
2018-04-08 23:08 ` L A Walsh
2018-04-09 18:30 ` Jordan Geoghegan
[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=8794ec10-dcee-4ad6-bfe6-3c8c108ca5f6@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).