Date: Mon, 22 May 2017 15:50:01 +0800 From: Julian Elischer <julian@freebsd.org> To: Allan Jude <allanjude@freebsd.org>, freebsd-current@freebsd.org Subject: Re: Ssh.. can we please have HPN back? Message-ID: <79d47e21-b8d8-b6d3-f6e7-92380f1358c4@freebsd.org> In-Reply-To: <abb2e3c6-bcf5-4e70-c2e2-8dce1f36c5e8@freebsd.org> References: <65e88d85-ca38-26dc-fe0a-910db11d470b@freebsd.org> <abb2e3c6-bcf5-4e70-c2e2-8dce1f36c5e8@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22/5/17 2:20 pm, Allan Jude wrote: > On 2017-05-18 22:28, Julian Elischer wrote: >> So after stripping out the HPN version of ssh from our product becasue >> "it was no longer needed" we dicovered that we were premature in doing so. >> Apparently ssh still really needs HPN to get any throughput at all when >> there are latencies involved. >> >> >> For example, with HPN we get 13MB/sec between the Azure US west >> Data center and the Azure East data center.But the standard ssh in 10.3 >> (with HPN stripped out) can barely manage 2MB/sec transfers. >> >> I did ask at the time whether it was proved that the new ssh didn't >> require the HPN changes, >> and was assured, "no" but it would appear that the picture isn't as clear. >> tht seems silly to have to import the port when we have what would >> otherwise be a >> perfectly good ssh as part of hte system, and it's really annoying >> having to specify >> /usr/local/bin/scp or /usr/local/bin/ssh in every script. >> >> So can we please have the latest version of the HPN changes back in the >> default system please? >> It seem rather odd that the upstream openssh has had this problem for SO >> LONG and not fixed it. >> >> Julian >> >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > I have this stand-alone patch ready now: > > https://github.com/openssh/openssh-portable/compare/master...allanjude:V_7_5_dynamic_window > > In my benchmarks with 100ms of latency (from dummynet) is increases SSH > send throughput from 1 megabyte/sec to 225 megabytes/sec provided a > large enough socket buffer. > > Still seeing lesser performance on the recv case, working on it. We have two patches of our own that upstream have ignored an option to set NoDelay and a pushwindow setting option (though I'm not sure the second is operational in the current code, it does apply with no errors...) The NoDelay options massively speeds up the case where you have chatty back and forth traffic (client/server) through a ssh tunnel. Are your changes against the sources in current? what about stable/10? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?79d47e21-b8d8-b6d3-f6e7-92380f1358c4>