From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Dean Hildebrand <seattleplus@gmail.com>,
linux-nfs@vger.kernel.org, aglo@citi.umich.edu
Subject: Re: [PATCH 0/1] SUNRPC: Add sysctl variables for server TCP snd/rcv buffer values
Date: Fri, 13 Jun 2008 16:56:20 -0400 [thread overview]
Message-ID: <20080613205620.GN8501@fieldses.org> (raw)
In-Reply-To: <C04F3083-91B2-464B-8F5C-958B243EB46C@oracle.com>
On Fri, Jun 13, 2008 at 02:51:18PM -0400, Chuck Lever wrote:
> On Jun 12, 2008, at 5:03 PM, Dean Hildebrand wrote:
>> I think the problem there is that the only way to set the buffer size
>> automatically would be to know the rtt and bandwidth of the network
>> connection. Excessive numbers of packets can get dropped if the TCP
>> buffer is set too large for a specific network connection.
>
>> In this case, the window opens too wide and lets too many packets out
>> into the system, somewhere along the path buffers start overflowing and
>> packets are lost, TCP congestion avoidance kicks in and cuts the window
>> size dramatically and performance along with it. This type of
>> behaviour creates a sawtooth pattern for the TCP window, which is less
>> favourable than a more steady state pattern that is created if the TCP
>> buffer size is set appropriately.
>
> Agreed it is a performance problem, but I thought some of the newer TCP
> congestion algorithms were specifically designed to address this by not
> closing the window as aggressively.
>
> Once the window is wide open, then, it would appear that choosing a good
> congestion avoidance algorithm is also important.
Any references for Olga or I to read on that sort of behavior?
--b.
next prev parent reply other threads:[~2008-06-13 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 18:54 [PATCH 0/1] SUNRPC: Add sysctl variables for server TCP snd/rcv buffer values Dean Hildebrand
2008-06-11 19:48 ` Chuck Lever
2008-06-11 21:01 ` Talpey, Thomas
2008-06-12 21:03 ` Dean Hildebrand
2008-06-13 18:51 ` Chuck Lever
2008-06-13 20:56 ` J. Bruce Fields [this message]
2008-06-14 1:07 ` Dean Hildebrand
2008-06-16 18:59 ` Chuck Lever
2008-06-17 22:03 ` Dean Hildebrand
2008-06-18 21:32 ` Chuck Lever
2008-06-25 1:06 ` Dean Hildebrand
2008-06-13 20:53 ` J. Bruce Fields
2008-06-13 23:58 ` Dean Hildebrand
2008-06-16 17:59 ` J. Bruce Fields
2008-06-18 18:33 ` Dean Hildebrand
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=20080613205620.GN8501@fieldses.org \
--to=bfields@fieldses.org \
--cc=aglo@citi.umich.edu \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=seattleplus@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.