From: Ed W <lists@wildgooses.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Raise initial congestion window size / speedup slow start?
Date: Wed, 14 Jul 2010 19:32:55 +0100 [thread overview]
Message-ID: <4C3E02D7.3080500@wildgooses.com> (raw)
In-Reply-To: <4C3DD5EB.9070908@tmr.com>
>> Does someone have some pointers on where to look to modify initial
>> congestion window please?
>>
> Are you sure that's the issue? The backlog is in incoming, is it not?
Well, I was simplifying a little bit, actually I have a bunch of
protocols in use, http is one of them
> Having dealt with moderately long delays push TB between timezones,
> have you set your window size up? Set
> /proc/sys/net/ipv4/tcp_adv_win_scale to 5 or 6 and see if that helps.
> You may have to go into /proc/sys/net/core and crank up the rmem_*
> settings, depending on your distribution.
>
> This allows the server to push a lot of data without an ack, which is
> what you want, the ack will be delayed by the long latency, so this helps.
I think I'm misunderstanding something fundamental here:
- Surely the limited congestion window is what throttles me at
connection initialisation time and this will not be affected by changing
the params you mention above? For sure the sliding window will be
relevant vs my bandwidth delay product once the tcp connection reaches
steady state, but I'm mostly worried here about performance right at the
creation of the connection?
- Both you and Alan mention that the bulk of the traffic is "incoming" -
this implies you think it's relevant? Obviously I'm missing something
fundamental here because my understanding is that the congestion window
shuts us down in both directions (at the start of the connection?)
Thanks for the replies - I will take it over to netdev
Ed W
next prev parent reply other threads:[~2010-07-14 18:32 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 10:43 Raise initial congestion window size / speedup slow start? Ed W
2010-07-14 11:58 ` Alan Cox
2010-07-14 15:21 ` Bill Davidsen
2010-07-14 18:15 ` 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
2010-07-14 18:32 ` Ed W [this message]
2010-07-15 15:10 ` Bill Davidsen
2010-07-16 2:58 ` Henrique de Moraes Holschuh
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=4C3E02D7.3080500@wildgooses.com \
--to=lists@wildgooses.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@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