Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] testing cake at 55mbit down/5mbit up
Date: Tue, 5 May 2015 12:56:22 -0700	[thread overview]
Message-ID: <CAA93jw4XwsadOQfAFdgx=CRgzV+UUKGqaqQm_aUMAm23iu+wOQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5F28YuQxx0pxYjQYPtuHxSsB7kY8t5_Kr1yJR7LX3uQw@mail.gmail.com>

The behavior is repeatable. I guess I will have to do a detailed exploration
of the captures. Perhaps this kernel or the one on the remote server has issues.

Linux lakshmi 3.16.0-31-lowlatency #43-Ubuntu SMP PREEMPT Tue Mar 10
17:56:21 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

On Tue, May 5, 2015 at 12:43 PM, Dave Taht <dave.taht@gmail.com> wrote:
> http://snapon.lab.bufferbloat.net/~d/prio_cake/
>
> I did have one massively anomalous result, on the 6vs4compete test,
> where it had a crazy high number of drops.
>
> The rest looked pretty sane although the diffserv4 thing did not line
> up with the markings netperf-wrapper is using for the rrul test.
>
> qdisc cake 801f: root refcnt 2 bandwidth 5Mbit diffserv4 flows
>  Sent 40103696 bytes 150518 pkt (dropped 11579, overlimits 449993 requeues 0)
>  backlog 0b 0p requeues 0
>            Class 0     Class 1     Class 2     Class 3
>   rate         5Mbit    4687Kbit    3750Kbit    1250Kbit
>   target       5.0ms       5.0ms       5.0ms      14.5ms
> interval     105.0ms     105.0ms     105.0ms     116.3ms
> Pk delay      52.7ms       7.5ms       1.9ms       1.1ms
> Av delay      21.5ms       4.5ms       118us        39us
> Sp delay       2.3ms         1us       108us        20us
>   pkts         66383       95449         103         162
> way inds           0           0           0           0
> way miss           5          39         103           5
> way cols           0           0           0           0
>   bytes      9484277    31571621       11481       10311
>   drops        11572           7           0           0
>   marks         2429         745           0           0
> qdisc ingress ffff: parent ffff:fff1 ----------------
>  Sent 406045781 bytes 293044 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
>
>
> --
> Dave Täht
> Open Networking needs **Open Source Hardware**
>
> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67



-- 
Dave Täht
Open Networking needs **Open Source Hardware**

https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67

  reply	other threads:[~2015-05-05 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-05 19:43 Dave Taht
2015-05-05 19:56 ` Dave Taht [this message]
2015-05-05 20:17 ` Dave Taht
2015-05-06 23:48 ` 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='CAA93jw4XwsadOQfAFdgx=CRgzV+UUKGqaqQm_aUMAm23iu+wOQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --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