From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Cc: jgeoghegan60@gmail.com
Subject: Re: Network Performance?
Date: Sun, 25 Mar 2018 10:24:00 -0000 [thread overview]
Message-ID: <5AB6E770.8020603@tlinx.org> (raw)
In-Reply-To: <5AB5825C.8060309@tlinx.org>
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?
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
---
Some additional notes..."/h" is my home directory on the
linux server, so 'bin/iotest is a script in my linux home dir.
The speeds / values using 'Bytes', (2**3) use the base2
prefixes for consistency. To get values in mbits, multiple
by 8.388608.
The above test only tests transfer speed -- not file i/o --
it uses /dev/zero for a source and /dev/null for a target.
To simplify testing, I created devices 'zero' and 'null'
in my home directory:
(on linux):
> ll zero null
crwxrw-rw- 1 1, 3 May 20 2016 null
crw-rw-rw- 1 1, 5 Jun 15 2015 zero
(on cygwin):
/h> ll zero null
-rwxrw-rw- 1 0 May 20 2016 null*
-rw-rw-rw- 1 0 Jun 15 2015 zero
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.
Flags for reading: iflag=fullblock conv=nocreat
and for writing: oflag=direct iflag=fullblock conv=nocreat,notrunc
To test the cpu-bounding, I just tried limiting the clock speeds
on the client and server.
Limiting the linux-server's max cpu-speed had
the most affect on performance:
(limited to 1.6GHz instead of 2.4GHz) (33% limitation)
Using bs=16.0M, count=256, iosize=4.0G (~35% slowdown)
R:4294967296 bytes (4.0GB) copied, 10.4467 s, 392MB/s
W:4294967296 bytes (4.0GB) copied, 21.5026 s, 190MB/s
Limiting the client (cygwin-win7sp1x64): (~7-13% slowdown)
(clock limited to 1.16GHz instead of 3.2)
Using bs=16.0M, count=256, iosize=4.0G
R:4294967296 bytes (4.0GB) copied, 7.14355 s, 573MB/s
W:4294967296 bytes (4.0GB) copied, 15.9781 s, 256MB/s
This would indicate that even in the unencrypted case
network transfer speed is cpu bound (and this is using
Jumbo packets).
--
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-25 0:04 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 [this message]
2018-03-27 3:54 ` Jordan Geoghegan
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=5AB6E770.8020603@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
--cc=jgeoghegan60@gmail.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).