All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: "Injong Rhee" <rhee@eos.ncsu.edu>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH] CUBIC v2.3 with new improved slow start
Date: Wed, 29 Oct 2008 15:39:28 -0700	[thread overview]
Message-ID: <20081029153928.3d47e26f@extreme> (raw)
In-Reply-To: <006001c93a0d$477d4e30$4a580e98@ncsu2cc0c3fa00>

On Wed, 29 Oct 2008 17:28:26 -0400
"Injong Rhee" <rhee@eos.ncsu.edu> wrote:

> I am releasing a new patch for CUBIC. This patch implements a new slow start 
> mechanism called HyStart. There were some discussions in the mailing list on 
> the poor performance of TCP slow start; our patch addresses those 
> performance issues arising from slow start.  For more information, please 
> refer to the following technical report:
> 
>  Sangtae Ha and Injong Rhee, "Taming the Elephants: New TCP Slow
> Start", NCSU Technical Report 2008. Available at
> http://netsrv.csc.ncsu.edu/export/hystart_techreport_2008.pdf
> 
> 
> The new update improves the start-up throughput of CUBIC substantially by 
> avoiding system overloading during slow start and shortening the 
> fast-recovery period after slow start. The key performance issues arising 
> when Linux is used with Windows XP or FreeBSD receivers are also addressed. 
> Our tests over Internet2 paths are very encouraging. The scheme is verified 
> to work well even for asymmetric paths,  with diverse receiver settings of 
> delayed acknowledgements, and with various operating systems (Windows XP and 
> FreeBSD). You can find the testing results from
> 
> http://netsrv.csc.ncsu.edu/wiki/index.php/TCP_Testing
> 
> Please let us know if there are other performance issues of TCP that you 
> want us to look into.
> 
> Injong and Sangtae.
> 

This looks like a good optimization, it obviously needs more testing
because Linux always seems to find new broken hardware.  The areas
that need to be tested should include:
  * MacOs has a broken version of delayed ack that might cause
    HyStart to radically underestimate.
  * Applications that dribble out packets might get better (or
    worse) performance.  This include dumb web servers.
  * Does this increase or reduce latency when using TCP for
    applications which never fill the congestion window? (games, financial, etc).

  reply	other threads:[~2008-10-29 22:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 21:28 [PATCH] CUBIC v2.3 with new improved slow start Injong Rhee
2008-10-29 22:39 ` Stephen Hemminger [this message]
2008-10-29 23:14   ` Injong Rhee
2008-10-29 23:40     ` Stephen Hemminger
2008-10-29 23:53       ` Rick Jones
2008-10-30  0:54         ` Injong Rhee
2008-10-30  1:08         ` Rick Jones
2008-10-29 23:45     ` David Miller
2008-10-30 15:36 ` [PATCH] tcp: mark BIC as experimental Stephen Hemminger
2008-10-31  7:50   ` David Miller
2008-10-31 16:41     ` Stephen Hemminger
2008-10-31 19:04       ` David Miller
2008-10-31 19:16     ` [RFC] tcp: make H-TCP the default congestion control Stephen Hemminger
2008-10-31 19:43       ` Sangtae Ha
2008-10-31 20:02         ` rhee
2008-11-02  4:29       ` David Miller
2008-11-02  7:27 ` [PATCH] CUBIC v2.3 with new improved slow start David Miller
2008-11-03 22:19   ` Sangtae Ha
2008-11-03 22:49     ` Stephen Hemminger
2008-11-04  1:12     ` David Miller

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=20081029153928.3d47e26f@extreme \
    --to=shemminger@vyatta.com \
    --cc=netdev@vger.kernel.org \
    --cc=rhee@eos.ncsu.edu \
    /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.