General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Fred Baker <fredbakersba@gmail.com>
To: Richard Scheffenegger <rscheff@gmx.at>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Goodput fraction w/ AQM vs bufferbloat
Date: Sun, 8 May 2011 20:07:21 -0700	[thread overview]
Message-ID: <866DFCDD-08FA-437D-8DDD-AAB039236A5E@gmail.com> (raw)
In-Reply-To: <77252BEA3E694F5092DA205BE5E691A1@srichardlxp2>


On May 8, 2011, at 5:34 AM, Richard Scheffenegger wrote:
> Goodput can really only be measured at the sender; by definition, any retransmitted packet will reduce goodput vs throughput; In your example, where each segment is retransmitted once, goodput would be - at most - 0.5, not 1.0... IMHO defining the data volume after the bottleneck by itself as goodput is also a bit short-sighted, because a good fraction of that data may still be discarded by TCP for numerous reasons, ultimately (ie, legacy go-back-n RTO recovery by the sender)...

Actually, I didn't say that every packet was retransmitted once. I said that every dropped packet was retransmitted once. And Goodput will never exceed the bit rate of the bottleneck in the path, apart from compression (which in effect applies a multiplier to the bottleneck bandwidth).

> But back to my original question: When looking at modern TCP stacks, with TSO, if the bufferbloat allows the senders cwnd to grow beyond thresholds which allow the aggressive use of TSO (64kB or even 256kB of data allowed in the senders cwnd), the effective sending rate of such a burst will be wirespeed (no interleaving segments of other sessions). As pointed out in other mails to this thread, if the bottleneck has then 1/10th the capacity of the senders wire (and is potentially shared among multiple senders), at least 90% of all the sent data of such a TSO segment train will be dropped in a single burst of loss... With proper AQM, and some (single segment) loss earlier, cwnd may never grow to trigger TSO in that way, and the goodput (1 segment out of 64kB data, vs. 58kB out of 64kB data) is obviously shifted extremely to the scenario with AQM...

Again, possibly, but not necessarily. If we have a constrained queue and are using tail drop, it is possible for a single burst sent to a full queue to be entirely lost. The question is, in the course of a file transfer, how many packets are lost. Before you make sweeping statements, I would strongly suggest that you mock up the situation and take a tcpdump.


      reply	other threads:[~2011-05-09  3:01 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
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 [this message]

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=866DFCDD-08FA-437D-8DDD-AAB039236A5E@gmail.com \
    --to=fredbakersba@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=rscheff@gmx.at \
    /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