From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: SSH/SFTP Network Performance?
Date: Sat, 24 Mar 2018 00:57:00 -0000 [thread overview]
Message-ID: <5AB5825C.8060309@tlinx.org> (raw)
In-Reply-To: <a45d39ab-93e1-41d5-22c7-40a61e355fd5@gmail.com>
Jordan Geoghegan wrote:
>
> Has anyone ever successfully transferred 150Mbps or more over the
> network using scp/sftp/rsync etc on Cygwin?
----
My experience was to use the cifs protocol as easiest (over local
network). With a 10Gb (limited to 8Gb due to running on older
PCIe interface) card, I'm getting:
/h> bin/iotest
Using bs=16.0M, count=64, iosize=1.0G
R:1073741824 bytes (1.0GB) copied, 1.67486 s, 611MB/s
W:1073741824 bytes (1.0GB) copied, 4.01592 s, 255MB/s
That's on a Win7 client to a linux-samba server.
If you want to get better results over SSH, you need to
have a custom ssh that allows a null encryption for block
transfers. See https://www.psc.edu/hpn-ssh.
Encryption really slows things down.
Also, on a local net, using Jumbo packets also helps
(I have a 9000 mtu on my local net).
--
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-23 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 22:40 Jordan Geoghegan
2018-03-24 0:57 ` L A Walsh [this message]
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
[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=5AB5825C.8060309@tlinx.org \
--to=cygwin@tlinx.org \
--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).