Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: [Cake] Cake strange behaviour
Date: Sat, 16 Jul 2016 10:35:43 +0100	[thread overview]
Message-ID: <5789FFEF.9010408@darbyshire-bryant.me.uk> (raw)

Hi guys,

Encountering some behaviour that I don't understand.  Line is a 40/10 
cake limited to 39000/9840. Overheads 12, 'dual-dsthosts' in ingress, 
'dual-srcshosts' on engress - limiting the on the WAN line. Take a look 
at my ping response graph

http://www.thinkbroadband.com/ping/share/9822cb5160582fa6abee29b60d807766-16-07-2016.html

Around 20:30 I fired up a windows machine that was behind on its updates 
so it generated a bit of ingress traffic.  Note the comparatively high 
latency (40ms) and stupidly high ping packet loss (50%)  The 3-5ms 
steady (blue) latency you can see is a system backup (so egress traffic) 
running till around 23:00.

The really strange bit is that cake stats show it has only dropped 10 
(yes 10!) packets.

I'm not the only person encountering 'interesting' behaviour with regard 
to windows updates inducing high latency and high packet loss.  It's as 
if cake weren't there managing flows and this is the ISP's rate limiter 
in action.

Kevin


             reply	other threads:[~2016-07-16  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-16  9:35 Kevin Darbyshire-Bryant [this message]
2016-07-16 10:59 ` Dave Täht
2016-07-16 11:53   ` Kevin Darbyshire-Bryant
2016-07-16 12:44     ` Dave Täht
2016-07-16 13:37     ` Sebastian Moeller
2016-07-16 16:25 ` Jonathan Morton

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=5789FFEF.9010408@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@lists.bufferbloat.net \
    /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