From owner-freebsd-current@freebsd.org Mon May 22 06:21:02 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4E97D780C6 for ; Mon, 22 May 2017 06:21:02 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B2DB1AEE for ; Mon, 22 May 2017 06:21:01 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 098E91363B for ; Mon, 22 May 2017 06:20:55 +0000 (UTC) Subject: Re: Ssh.. can we please have HPN back? To: freebsd-current@freebsd.org References: <65e88d85-ca38-26dc-fe0a-910db11d470b@freebsd.org> From: Allan Jude Message-ID: Date: Mon, 22 May 2017 02:20:50 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <65e88d85-ca38-26dc-fe0a-910db11d470b@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3wjPWbQjFw2GOKfQicCnMVqn4hPN3gcVM" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2017 06:21:02 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3wjPWbQjFw2GOKfQicCnMVqn4hPN3gcVM Content-Type: multipart/mixed; boundary="DeBn3DwctKFeJaWQarxqiTqtLA5uf878K"; protected-headers="v1" From: Allan Jude To: freebsd-current@freebsd.org Message-ID: Subject: Re: Ssh.. can we please have HPN back? References: <65e88d85-ca38-26dc-fe0a-910db11d470b@freebsd.org> In-Reply-To: <65e88d85-ca38-26dc-fe0a-910db11d470b@freebsd.org> --DeBn3DwctKFeJaWQarxqiTqtLA5uf878K Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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. >=20 >=20 > 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. >=20 > 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 cle= ar. > 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. >=20 > 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 S= O > LONG and not fixed it. >=20 > Julian >=20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" 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. --=20 Allan Jude --DeBn3DwctKFeJaWQarxqiTqtLA5uf878K-- --3wjPWbQjFw2GOKfQicCnMVqn4hPN3gcVM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJZIoNGAAoJEBmVNT4SmAt+Qf4QAN3iP5mudGpYPgHHIXOGfozQ zX71OmzgxHgs47KI/ba8QUObShc6yb2hvhBCEVxB4L9uz3UbNRkHyighwpVgIMiL CTZrmpbBOjuXF8L4Ltl+dUBym0JQkbqdIenAkkE9RMYkCZgHibevePVCCNMLKh8M qeMN49+ZsOZuagMWV+W6sZBCFjB211yWckJXXPa68YsbI9GNCkZ4UfbWYIsGbaOh oe6E/vSW0VR8qKA5iMapGZrVSllk0CNhfHCWihlwO2+4AV0LzilfFiRkWU0gkN38 eBK5vstRMP/G60QRhlRtxojY80zVjvZ6dzfiyxKN36gn0KmVYg/sr6CudpPnfl+r lfsprQcb+SU3fF6BTVil8soTDsiln+haXWK/ncxy0AAnZPu8Gwqfw9XKoS8+ZYPK DIN/gNZtKaGqlTO+tjqdWdqvLXd+WGuCvAL54RMRUUPvtCIQmIFL2XMs7HWHb9Xi 6caGLk8f/ser1X5VUzRag4MOWryjP4F9rR9mAp2XRPO0Hto5uO9LBM/DqayjyrdH fTbT//3bzxhI+4txIPBPQ8usn3EALFjI6fXYlMmkkQTiyIYsAjrrTHzjPaNlWGHp z/K1PZu5DDq8rWnhU9bQZ9U5vjPxbBWthEslEsnmDbm09UmwEVGsYzoSeyfm1dAD HXbiLHB1CvVT6g2d13LW =NG2z -----END PGP SIGNATURE----- --3wjPWbQjFw2GOKfQicCnMVqn4hPN3gcVM--