From: Stephen Hemminger <shemminger@vyatta.com>
To: Lucas Nussbaum <lucas.nussbaum@loria.fr>
Cc: Injong Rhee <rhee@ncsu.edu>, David Miller <davem@davemloft.net>,
xiyou.wangcong@gmail.com, netdev@vger.kernel.org,
sangtae.ha@gmail.com
Subject: Re: [PATCH] Make CUBIC Hystart more robust to RTT variations
Date: Wed, 9 Mar 2011 09:56:59 -0800 [thread overview]
Message-ID: <20110309095659.1373c296@s6510> (raw)
In-Reply-To: <20110309065319.GA23740@xanadu.blop.info>
On Wed, 9 Mar 2011 07:53:19 +0100
Lucas Nussbaum <lucas.nussbaum@loria.fr> wrote:
> On 08/03/11 at 20:30 -0500, Injong Rhee wrote:
> > Now, both tools can be wrong. But that is not catastrophic since
> > congestion avoidance can kick in to save the day. In a pipe where no
> > other flows are competing, then exiting slow start too early can
> > slow things down as the window can be still too small. But that is
> > in fact when delays are most reliable. So those tests that say bad
> > performance with hystart are in fact, where hystart is supposed to
> > perform well.
>
> Hi,
>
> In my setup, there is no congestion at all (except the buffer bloat).
> Without Hystart, transferring 8 Gb of data takes 9s, with CUBIC exiting
> slow start at ~2000 packets.
> With Hystart, transferring 8 Gb of data takes 19s, with CUBIC exiting
> slow start at ~20 packets.
> I don't think that this is "hystart performing well". We could just as
> well remove slow start completely, and only do congestion avoidance,
> then.
>
> While I see the value in Hystart, it's clear that there are some flaws
> in the current implementation. It probably makes sense to disable
> hystart by default until those problems are fixed.
What is the speed and RTT time of your network?
I think you maybe blaming hystart for other issues in the network.
next prev parent reply other threads:[~2011-03-09 17:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 9:32 [PATCH] Make CUBIC Hystart more robust to RTT variations Lucas Nussbaum
2011-03-08 10:21 ` WANG Cong
2011-03-08 11:10 ` Lucas Nussbaum
2011-03-08 15:26 ` Injong Rhee
2011-03-08 19:43 ` David Miller
2011-03-08 23:21 ` Stephen Hemminger
2011-03-09 1:30 ` Injong Rhee
2011-03-09 6:53 ` Lucas Nussbaum
2011-03-09 17:56 ` Stephen Hemminger [this message]
2011-03-09 18:25 ` Lucas Nussbaum
2011-03-09 19:56 ` Stephen Hemminger
2011-03-09 21:28 ` Lucas Nussbaum
2011-03-09 20:01 ` Stephen Hemminger
2011-03-09 21:12 ` Yuchung Cheng
2011-03-09 21:33 ` Lucas Nussbaum
2011-03-09 21:51 ` Stephen Hemminger
2011-03-09 22:03 ` Lucas Nussbaum
2011-03-10 5:24 ` Bill Fink
2011-03-10 6:17 ` Stephen Hemminger
2011-03-10 7:17 ` Bill Fink
2011-03-10 8:54 ` Lucas Nussbaum
2011-03-11 2:25 ` Bill Fink
2011-03-10 14:37 ` Injong Rhee
2011-03-09 1:33 ` Sangtae Ha
[not found] ` <AANLkTimdpEKHfVKw+bm6OnymcnUrauU+jGOPeLzy3Q0o@mail.gmail.com>
2011-03-08 18:14 ` Lucas Nussbaum
2011-03-10 23:28 ` Stephen Hemminger
2011-03-11 5:59 ` Lucas Nussbaum
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=20110309095659.1373c296@s6510 \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=lucas.nussbaum@loria.fr \
--cc=netdev@vger.kernel.org \
--cc=rhee@ncsu.edu \
--cc=sangtae.ha@gmail.com \
--cc=xiyou.wangcong@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.