Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: <erik.taraldsen@telenor.com>
To: <toke@toke.dk>
Cc: <moeller0@gmx.de>, <cake@lists.bufferbloat.net>
Subject: Re: [Cake] ER-X now running cake, thanks for the help. :)
Date: Fri, 5 May 2017 17:12:46 +0000	[thread overview]
Message-ID: <1494004366992.6614@telenor.com> (raw)
In-Reply-To: <661B553B-512D-4210-9CDF-0ADD1B21CE0C@toke.dk>

> Fra: Toke Høiland-Jørgensen <toke@toke.dk>
>
> Right, so you're measuring the actual latency experienced by the UDP packets in the 
> unresponsive flow? Yeah, you'll get quite a bit of latency in that case. But not sure that's a case 
> we should be optimising for...

That was just the worst case scenario, not really meant to emulate user traffic.  And I'm not suggesting that the schedulers should be optimized for that. But we can agree that 20+ seconds of delay is a bit much no matter how it is measured? :)

I also use nuttcp to model other kinds of traffic, such as VIOP, Voice over WiFi, dumb udp vod that Telenor uses.  Then I subject the router to various kinds of line saturation and stress.  Cloud upload, torrent, virus emulation (zmap not really designed for that, but man, if you want to inflict pain on a router... zmap is your daddy).  And we try to make sure that long living tcp/vpn sessions are not torn down due to need for more sessions in nat for yet another torrent session.  Different QoS/schedulers behave different and we try and use the best possible solution for a given HW/access tech.  What works very well for balancing cloud upload and interactive traffic like ssh or http may fail miserably on torrent.  And the other way around.  On our legacy stuff we can't implement fq_codel, cake or sfq even. 

And as you know I also incorporate flent. 


-Erik

  reply	other threads:[~2017-05-05 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 13:00 erik.taraldsen
2017-05-05 13:20 ` Toke Høiland-Jørgensen
2017-05-05 13:20 ` Sebastian Moeller
2017-05-05 13:55   ` erik.taraldsen
2017-05-05 13:59     ` Toke Høiland-Jørgensen
2017-05-05 14:30       ` erik.taraldsen
2017-05-05 15:23         ` Toke Høiland-Jørgensen
2017-05-05 17:12           ` erik.taraldsen [this message]
2017-05-05 19:29             ` Neil Shepperd
2017-05-05 14:06     ` Sebastian Moeller

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

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

  git send-email \
    --in-reply-to=1494004366992.6614@telenor.com \
    --to=erik.taraldsen@telenor.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --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