From: Constantine Dovrolis <dovrolis@cc.gatech.edu>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Goodput fraction w/ AQM vs bufferbloat
Date: Sat, 07 May 2011 23:04:31 -0400 [thread overview]
Message-ID: <4DC6083F.1080105@cc.gatech.edu> (raw)
In-Reply-To: <20110507171555.240f9f8f@nehalam>
Hi, I suggest you look at the following paper for a more
general version of this formula (equation 3), which includes the
effect of limited capacity and/or limited receive-window:
http://www.cc.gatech.edu/fac/Constantinos.Dovrolis/Papers/f235-he.pdf
The paper also discusses common mistakes when this formula is used
to predict the throughput of a TCP connection - the basic
idea is that we cannot use the loss rate *before* the start
of a TCP connection to predict what its throughput will be.
A large TCP connection that is not limited by its receive-window
can of course cause an increase in the loss rate of the path
that it traverses (see sections 3.2 - 3.4)
regards
Constantine
On 5/7/2011 8:15 PM, Stephen Hemminger wrote:
> On Sat, 7 May 2011 19:39:22 +0300
> Jonathan Morton<chromatix99@gmail.com> wrote:
>
>>
>> On 7 May, 2011, at 1:10 am, Stephen Hemminger wrote:
>>
>>> Rate<= (MSS/RTT)*(1 / sqrt{p})
>>>
>>> where:
>>> Rate: is the TCP transfer rate or throughputd
>>> MSS: is the maximum segment size (fixed for each Internet path, typically 1460 bytes)
>>> RTT: is the round trip time (as measured by TCP)
>>> p: is the packet loss rate.
>>
>> So if the loss rate is 1.0 (100%), the throughput is MSS/RTT. If the loss rate is 0, the throughput goes to infinity. That doesn't seem right to me.
>
> If loss rate is 0 there is no upper bound on TCP due to loss.
> There are other limits on TCP throughput like window size but not limits
> because of loss.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
Constantine
--------------------------------------------------------------
Constantine Dovrolis, Associate Professor
College of Computing, Georgia Institute of Technology
3346 KACB, 404-385-4205, dovrolis@cc.gatech.edu
http://www.cc.gatech.edu/~dovrolis/
next prev parent reply other threads:[~2011-05-08 2:58 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 17:05 [Bloat] Network computing article on bloat Dave Taht
2011-04-26 18:13 ` Dave Hart
2011-04-26 18:17 ` Dave Taht
2011-04-26 18:28 ` dave greenfield
2011-04-26 18:32 ` Wesley Eddy
2011-04-26 19:37 ` Dave Taht
2011-04-26 20:21 ` Wesley Eddy
2011-04-26 20:30 ` Constantine Dovrolis
2011-04-26 21:16 ` Dave Taht
2011-04-27 17:10 ` Bill Sommerfeld
2011-04-27 17:40 ` Wesley Eddy
2011-04-27 7:43 ` Jonathan Morton
2011-04-30 15:56 ` Henrique de Moraes Holschuh
2011-04-30 19:18 ` [Bloat] Goodput fraction w/ AQM vs bufferbloat Richard Scheffenegger
2011-05-05 16:01 ` Jim Gettys
2011-05-05 16:10 ` Stephen Hemminger
2011-05-05 16:30 ` Jim Gettys
2011-05-05 16:49 ` [Bloat] Burst Loss Neil Davies
2011-05-05 18:34 ` Jim Gettys
2011-05-06 11:40 ` Sam Stickland
2011-05-06 11:53 ` Neil Davies
2011-05-08 12:42 ` Richard Scheffenegger
2011-05-09 18:06 ` Rick Jones
2011-05-11 8:53 ` Richard Scheffenegger
2011-05-11 9:53 ` Eric Dumazet
2011-05-12 14:16 ` [Bloat] Publications Richard Scheffenegger
2011-05-12 16:31 ` [Bloat] Burst Loss Fred Baker
2011-05-12 16:41 ` Rick Jones
2011-05-12 17:11 ` Fred Baker
2011-05-13 5:00 ` Kevin Gross
2011-05-13 14:35 ` Rick Jones
2011-05-13 14:54 ` Dave Taht
2011-05-13 20:03 ` [Bloat] Jumbo frames and LAN buffers (was: RE: Burst Loss) Kevin Gross
2011-05-14 20:48 ` Fred Baker
2011-05-15 18:28 ` Jonathan Morton
2011-05-15 20:49 ` Fred Baker
2011-05-16 0:31 ` Jonathan Morton
2011-05-16 7:51 ` Richard Scheffenegger
2011-05-16 9:49 ` Fred Baker
2011-05-16 11:23 ` [Bloat] Jumbo frames and LAN buffers Jim Gettys
2011-05-16 13:15 ` Kevin Gross
2011-05-16 13:22 ` Jim Gettys
2011-05-16 13:42 ` Kevin Gross
2011-05-16 15:23 ` Jim Gettys
[not found] ` <-854731558634984958@unknownmsgid>
2011-05-16 13:45 ` Dave Taht
2011-05-16 18:36 ` Richard Scheffenegger
2011-05-16 18:11 ` [Bloat] Jumbo frames and LAN buffers (was: RE: Burst Loss) Richard Scheffenegger
2011-05-17 7:49 ` BeckW
2011-05-17 14:16 ` Dave Taht
[not found] ` <-4629065256951087821@unknownmsgid>
2011-05-13 20:21 ` Dave Taht
2011-05-13 22:36 ` Kevin Gross
2011-05-13 22:08 ` [Bloat] Burst Loss david
2011-05-13 19:32 ` Denton Gentry
2011-05-13 20:47 ` Rick Jones
2011-05-06 4:18 ` [Bloat] Goodput fraction w/ AQM vs bufferbloat Fred Baker
2011-05-06 15:14 ` richard
2011-05-06 21:56 ` Fred Baker
2011-05-06 22:10 ` Stephen Hemminger
2011-05-07 16:39 ` Jonathan Morton
2011-05-08 0:15 ` Stephen Hemminger
2011-05-08 3:04 ` Constantine Dovrolis [this message]
2011-05-08 13:00 ` Richard Scheffenegger
2011-05-08 12:53 ` Richard Scheffenegger
2011-05-08 12:34 ` Richard Scheffenegger
2011-05-09 3:07 ` Fred Baker
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DC6083F.1080105@cc.gatech.edu \
--to=dovrolis@cc.gatech.edu \
--cc=bloat@lists.bufferbloat.net \
--cc=shemminger@vyatta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox