DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=DEIVBjEuVfxC2i9k7wwYHLJ9yYJnm
	IUCvXKzK1+pNujHngRJYYdltjYHWCZxcRsu8xhbe1AGk+IeRFyITp1LHCBossOzp
	WlfkRo0KrifCsnQHNZc1JdLG2nDqqSBE1SR31N9mhampM29It8Xvf90DiiaHY1lf
	KphrYI1hfe0uL0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
From: Daniel Havey <dhavey@gmail.com>
Date: Mon, 28 Nov 2016 11:54:27 -0800
Message-ID: <CAO1c0AT52ZzCKc3yD_7eX6ri4VubrTb5L+X-4vHWoXBAX2jsfw@mail.gmail.com>
Subject: Cygwin TCP slow
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

Hello,
We have had complaints from several large hardware vendors that
Windows networking is slow for apps like iperf that are used to
measure throughput.  Iperf on Windows is compiled against the
cygwin1.dll.  We have root caused the problem to a couple of lines of
code in net.cc that set SO_RCVBUF and SO_SNDBUF to about 200KB.

The theoretical window/RTT plot for the buffer size set by Cygwin
(0x34000 = 200KB) gives us:
1ms -> 1703Mbps
2ms -> 851Mbps
3ms -> 567Mbps
4ms -> 425Mbps
5ms -> 340Mbps
6ms -> 283Mbps
7ms -> 243Mbps
8ms -> 212Mbps
9ms -> 189Mbps
10ms -> 170Mbps
20ms -> 85Mbps
40ms -> 42Mbps
60ms -> 28Mbps
80ms -> 21Mbps

We have confirmed this by experiment and also confirmed that the
limitation goes away if the buffers are not manually set.  Windows has
autotuning and when the buffers are set manually the autotuning is
disabled.  This is causing the throughput limitation.  So we would
like to formally ask that you please not manually set SO_RCVBUF or
SO_SNDBUF.

thanxs ;^)
...Daniel

--
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