General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Paolo Valente <paolo.valente@unimore.it>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bufferbloat effects on throughput
Date: Mon, 27 Apr 2015 14:45:08 +0200	[thread overview]
Message-ID: <C764875C-8CB7-44CA-A4CC-1DC951DEBC53@unimore.it> (raw)
In-Reply-To: <87pp6p22ho.fsf@toke.dk>


Il giorno 27/apr/2015, alle ore 14:13, Toke Høiland-Jørgensen <toke@toke.dk> ha scritto:

> Paolo Valente <paolo.valente@unimore.it> writes:
> 
>> Thanks. So, if I understood correctly, average throughput may or may
>> not be affected, but large throughput fluctuations will always occur
>> in the presence of bufferbloat.
> 
> I'm always wary of saying 'always', but I'd hazard an 'often' ;)
> 
>> Sorry for my usual refrain, but … any pointers to tests, results,
>> papers and the like?
> 
> Hmm, not sure if there's any papers dealing specifically with this.
> However, it's quite easy to provoke this behaviour. Compare, for
> instance,
> 
> http://files.toke.dk/bufferbloat/rrul-pfifo_fast-all_scaled.pdf
> 
> with
> 
> http://files.toke.dk/bufferbloat/rrul-fq_codel-all_scaled.pdf
> 
> The two top graphs on each are throughput (download and upload
> respectively).
> 

Thanks. The results shown in your graphs seem unmistakable …

One question: how can one be sure (if it is possible) that the fluctuation of the throughput of a TCP flow on a given node is caused by bufferbloat issues in the node, and not by other factors (such as, e.g., systematic drops in some other nodes along the path followed by the flow, with the drops possibly even caused by different reasons than bufferbloat)?

Thanks,
Paolo

> For the aggregate behaviour, I had some data on that in my presentation
> at the IETF in Hawaii:
> 
> http://www.ietf.org/proceedings/91/slides/slides-91-iccrg-4.pdf
> 
> -Toke


--
Paolo Valente                                                 
Algogroup
Dipartimento di Fisica, Informatica e Matematica		
Via Campi, 213/B
41125 Modena - Italy        				  
homepage:  http://algogroup.unimore.it/people/paolo/


  reply	other threads:[~2015-04-27 12:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  8:59 Paolo Valente
2015-04-27  9:20 ` Toke Høiland-Jørgensen
2015-04-27 12:01   ` Paolo Valente
2015-04-27 12:13     ` Toke Høiland-Jørgensen
2015-04-27 12:45       ` Paolo Valente [this message]
2015-04-27 13:01         ` Toke Høiland-Jørgensen
2015-04-27 14:19           ` Bill Ver Steeg (versteb)
2015-04-27 17:28             ` Dave Taht
2015-04-27 19:51               ` Bill Ver Steeg (versteb)

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=C764875C-8CB7-44CA-A4CC-1DC951DEBC53@unimore.it \
    --to=paolo.valente@unimore.it \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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