Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Noah <n0manletter@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Question About Sparse Flow Latency
Date: Mon, 7 Mar 2016 16:48:31 -0500	[thread overview]
Message-ID: <56DDF72F.1010503@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

Hi,

I have a question about cake's sparse flow latency.

I've been using cake for a while now.  I use dual flow isolation on my 
LAN, so I shape my LAN interface. When I download a game on steam, I 
have about 11-16 bulk flows. I use the command: *watch -n 1 tc -s qdisc 
show dev eth1* to see my qdisc stats refreshed every second.  I notice 
that I will see sparse delays of 13-22 ms often.

Is that normal, and what are common sparse delays I should be seeing 
under that load?

I have tried using HTB + FQ_Codel, and I don't see the latency spikes I 
have with cake.

I am using an archer c7 shaped to 60 mbps down 9 mbps up + ECN.

CPU load about 60-80%.

Thank you,

Noah


[-- Attachment #2: Type: text/html, Size: 1997 bytes --]

                 reply	other threads:[~2016-03-07 21:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=56DDF72F.1010503@gmail.com \
    --to=n0manletter@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