CoDel AQM discussions
 help / color / mirror / Atom feed
From: Andrew McGregor <andrewmcgr@gmail.com>
To: divya singla <divyasingla1989@gmail.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] Different scenarios for seeing bufferbloat
Date: Thu, 16 Apr 2015 14:08:36 +1000	[thread overview]
Message-ID: <CAA_e5Z5GRb0yOjB=Cug1f6_Q-Jn+CgoVqDpJ1UheY18chzf28w@mail.gmail.com> (raw)
In-Reply-To: <CAONkte-Luj3y=M_7y-mH3TM+c1NHexT1GSy3wZFgdLHz9vadew@mail.gmail.com>

Why don't you try a few scenarios and see where the bloat starts to
show up, based on a realistic home scenario?  It's pretty easy to
demonstrate in the real world, so you shouldn't have too much trouble
in a simulation.

On Wed, Apr 15, 2015 at 1:04 AM, divya singla <divyasingla1989@gmail.com> wrote:
> please give me some ideas for ftp/cbr traffic with dumb-bell topology.
> what should be delay and bandwidth for bottleneck link and for other links?
> How many traffic sources should be there?
>
>
>
> On Tue, Apr 14, 2015 at 1:52 PM, Andrew McGregor <andrewmcgr@gmail.com>
> wrote:
>>
>> The canonical examples are home connections, DSL or cable, with say a
>> couple of thousand packets of buffer for a 10 Mbps down 2 Mbps up
>> asymmetrical connection.  That should easily demonstrate what you are
>> looking for.
>>
>> On Tue, Apr 14, 2015 at 4:57 AM, divya singla <divyasingla1989@gmail.com>
>> wrote:
>> > Hi Members,
>> >
>> > Please tell me what would be appropriate  simulation scenarios for
>> > bufferbloat problem ?
>> >
>> >
>> >
>> > _______________________________________________
>> > Codel mailing list
>> > Codel@lists.bufferbloat.net
>> > https://lists.bufferbloat.net/listinfo/codel
>> >
>
>

  reply	other threads:[~2015-04-16  4:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 18:57 divya singla
2015-04-14  8:22 ` Andrew McGregor
2015-04-14 15:04   ` divya singla
2015-04-16  4:08     ` Andrew McGregor [this message]
2015-04-15 12:38 Rich Brown

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/codel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA_e5Z5GRb0yOjB=Cug1f6_Q-Jn+CgoVqDpJ1UheY18chzf28w@mail.gmail.com' \
    --to=andrewmcgr@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=divyasingla1989@gmail.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