From: Jordan Geoghegan <jgeoghegan60@gmail.com>
To: cygwin@cygwin.com
Subject: SSH/SFTP Network Performance?
Date: Fri, 23 Mar 2018 22:40:00 -0000 [thread overview]
Message-ID: <a45d39ab-93e1-41d5-22c7-40a61e355fd5@gmail.com> (raw)
Hi folks,
First time poster here. I was hoping others could weigh in with their
experiences running an ssh/sftp server from Cygwin.
tl;dr
Has anyone ever successfully transferred 150Mbps or more over the
network using scp/sftp/rsync etc on Cygwin?
For a more in depth explanation, see below:
I have been experimenting with transferring data from my Windows
machines through various methods, and was hoping to use rsync as that is
what I use for backing up my other machines. During my testing, I have
unfortunately been unable to push more than ~8MB/s (~60 megabits per
second) regardless of the cipher (aes-gcm, aes-ctr, chacha20 etc) or
transfer method (scp, sftp or rsync). All of them seem to be hitting
some sort of bottleneck, with sftp being marginally faster than the others.
I am backing up to an OpenBSD file server on the local LAN. Using
OpenBSD ---> OpenBSD (or Linux, MacOS etc) I can saturate the 1Gbit
interface no problem. When using the built in Windows file sharing, I
can also saturate the interface.
The fastest ssh transfer speed I have managed from Windows has been
using various proprietary offerings such as the Bitvise ssh server or
the SSH NetDrive sftp network drive mounter utility. Both of these tools
also seem to hit some sort of bottlneck, though around ~18MB/s (~150
megabit max as per Task Manager) for Bitvise, and around ~24MB/s (~200
megabit max) with SSH netdrive.
Task Manager shows less than 5% cpu and disk usage, with only a slight
bump up to 7% when using chacha20, I presume due to the lack of AES-NI
for chacha. The machine is an i3 with an SSD and an Intel NIC so I am
scratching my head as to what the issue could be. Cygwin will saturate
my my 150Mbit WAN link in any direction over https no problem as well,
which is interesting.
So, that's my story. Has anyone had any luck pushing beyond 150 megabits
via ssh from/to Cygwin?
--
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 reply other threads:[~2018-03-23 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 22:40 Jordan Geoghegan [this message]
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
[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=a45d39ab-93e1-41d5-22c7-40a61e355fd5@gmail.com \
--to=jgeoghegan60@gmail.com \
--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).