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:01:24 +0200	[thread overview]
Message-ID: <2B5B39C9-A33D-46ED-84C6-56F237284B21@unimore.it> (raw)
In-Reply-To: <87zj5u2aho.fsf@toke.dk>


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

> Paolo Valente <paolo.valente@unimore.it> writes:
> 
>> If there are, could anyone please point me to further reading on these
>> aspects?
> 
> Bufferbloat can definitely adversely affect throughput in some cases.
> Mainly because it causes throughput to oscillate: when the queue fills,
> a lot of data can be dropped at once, causing throughput to drop, which
> takes a while to recover. This can degrade aggregate throughput. Having
> smart queueing smoothes out the traffic, so the oscillations are lower
> and average throughput thus better.
> 
> The effect is most visible when you have several flows sharing a link:
> when the (FIFO) queue fills, they will tend to all experience drops at
> once, and so all slow down.
> 

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.

Sorry for my usual refrain, but … any pointers to tests, results, papers and the like?

Thanks,
Paolo

> -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:01 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 [this message]
2015-04-27 12:13     ` Toke Høiland-Jørgensen
2015-04-27 12:45       ` Paolo Valente
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=2B5B39C9-A33D-46ED-84C6-56F237284B21@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