From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Raise initial congestion window size / speedup slow start?
Date: Thu, 15 Jul 2010 19:14:24 -0400 [thread overview]
Message-ID: <4C3F9650.1040800@tmr.com> (raw)
In-Reply-To: <20100714.111553.104052157.davem@davemloft.net>
David Miller wrote:
> From: Bill Davidsen <davidsen@tmr.com>
> Date: Wed, 14 Jul 2010 11:21:15 -0400
>
>> You may have to go into /proc/sys/net/core and crank up the
>> rmem_* settings, depending on your distribution.
>
> You should never, ever, have to touch the various networking sysctl
> values to get good performance in any normal setup. If you do, it's a
> bug, report it so we can fix it.
>
> I cringe every time someone says to do this, so please do me a favor
> and don't spread this further. :-)
>
I think transit time measured in 1/10th sec would disqualify this as a "normal
setup."
High bandwidth and high latency don't work well because you get "send until the
window is full then wait for ack" and poor performance. I saw this with sat feed
to Wyoming from GE's Research Center in upstate NY in the late 80's or early
90's. (I think this was NYserNet at that time). I did feeds from NYC area to
California and Hawaii with SBC in the early to mid 2k years. In every case
SunOS, Solaris, AIX and Linux all failed to hit anything like reasonable
transfer speeds without manually tweaking, and I got the advice on increasing
window size from network engineers at ISPs and backbone providers.
The O.P. may have other issues, and may benefit from doing other things as well,
but raising window size is a reasonable thing to do on links with RTT in
hundreds of ms, and it's easy to try without changing config files.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
prev parent reply other threads:[~2010-07-15 23:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C3D94E3.9080103@wildgooses.com>
[not found] ` <4C3DD5EB.9070908@tmr.com>
2010-07-14 18:15 ` Raise initial congestion window size / speedup slow start? David Miller
2010-07-14 18:48 ` Ed W
2010-07-14 19:10 ` Stephen Hemminger
2010-07-14 21:47 ` Mitchell Erblich
2010-07-14 20:17 ` Rick Jones
2010-07-14 20:39 ` Hagen Paul Pfeifer
2010-07-14 21:55 ` David Miller
2010-07-14 22:13 ` Hagen Paul Pfeifer
2010-07-14 22:19 ` Rick Jones
2010-07-14 22:40 ` Hagen Paul Pfeifer
2010-07-14 22:52 ` Ed W
2010-07-14 23:01 ` Hagen Paul Pfeifer
2010-07-14 23:05 ` Ed W
2010-07-15 3:49 ` Bill Fink
2010-07-15 5:29 ` H.K. Jerry Chu
2010-07-15 19:51 ` Rick Jones
2010-07-15 20:48 ` Stephen Hemminger
2010-07-16 0:23 ` H.K. Jerry Chu
2010-07-16 9:03 ` Hagen Paul Pfeifer
2010-07-15 10:33 ` Alan Cox
2010-07-14 22:05 ` Ed W
2010-07-14 22:36 ` Hagen Paul Pfeifer
2010-07-14 23:01 ` Ed W
2010-07-15 4:12 ` Tom Herbert
2010-07-15 7:48 ` Ed W
2010-07-15 17:36 ` Jerry Chu
2010-07-15 5:09 ` H.K. Jerry Chu
2010-07-15 2:52 ` Bill Fink
2010-07-15 4:51 ` H.K. Jerry Chu
2010-07-16 17:01 ` Patrick McManus
2010-07-16 17:41 ` Ed W
2010-07-17 1:23 ` H.K. Jerry Chu
2010-07-17 0:36 ` H.K. Jerry Chu
2010-07-19 17:08 ` Rick Jones
2010-07-19 22:51 ` H.K. Jerry Chu
2010-07-19 23:42 ` Hagen Paul Pfeifer
2010-07-15 23:14 ` Bill Davidsen [this message]
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=4C3F9650.1040800@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 NNTP newsgroup(s).