Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: galene@lists.galene.org, Dave Taht <dave@taht.net>
Subject: [Galene] Re: fq-codel trashing
Date: Tue, 12 Jan 2021 09:42:44 -0800	[thread overview]
Message-ID: <CAA93jw6PN2nmgg3An-xkxc0bXxG+qV2k29oHRO14xB_y5DCAhg@mail.gmail.com> (raw)
In-Reply-To: <878s8yqcmh.wl-jch@irif.fr>

On Tue, Jan 12, 2021 at 9:38 AM Juliusz Chroboczek <jch@irif.fr> wrote:
>
> >> We're having a large meeting on the lab's Galène server, and it looks like
> >> fq-codel is trashing: the new_flow_count increases as fast as the packet
> >> counter.
>
> > That just sounds like wherever you're running FQ-CoDel is not actually
> > the bottleneck?
>
> Right.
>
> > But it only happens if you're also running a shaper (such as HTB or TBF)
> > on the interface, since if FQ-CoDel is installed on a physical interface
> > it will set the TCQ_F_CAN_BYPASS flag, which means that when the queue
> > is completely empty it will be bypassed entirely...
>
> I'm not running a shaper.  The interface is reported as
>
>     00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
>
> Ethtool doesn't give anything interesting.
>
> Here's the output of tc -s qdisc show:
>
>     qdisc fq_codel 0: root refcnt 2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
>      Sent 1270306213261 bytes 3032714775 pkt (dropped 2839148, overlimits 0 requeues 10623)
>      backlog 0b 0p requeues 10623
>       maxpacket 68130 drop_overlimit 1576971 new_flow_count 732081615 ecn_mark 22
>       new_flows_len 0 old_flows_len 0

Nice to see drops and marks.

IF you have spare cpu, you can also run cake native no shaper and
strip gro (maxpacket 64k indicates gro is on). On the other
hand, gro is saves on context switches in vms.

> _______________________________________________
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org



-- 
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman

dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729

  reply	other threads:[~2021-01-12 17:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 13:46 [Galene] " Juliusz Chroboczek
2021-01-12 15:55 ` [Galene] " Toke Høiland-Jørgensen
2021-01-12 16:01   ` Dave Taht
2021-01-12 17:38   ` Juliusz Chroboczek
2021-01-12 17:42     ` Dave Taht [this message]
2021-01-12 18:10       ` Juliusz Chroboczek
2021-01-12 19:05         ` Dave Taht
2021-01-12 19:52           ` Michael Ströder
2021-01-12 21:02           ` Juliusz Chroboczek
2021-01-12 19:29         ` Michael Ströder
2021-01-12 21:22           ` Juliusz Chroboczek
2021-01-13 19:09             ` Michael Ströder
2021-01-14 12:59               ` Juliusz Chroboczek
2021-01-14 13:03                 ` Michael Ströder
2021-01-14 13:10                   ` Juliusz Chroboczek
2021-01-14 13:23                     ` Michael Ströder

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.galene.org/postorius/lists/galene.lists.galene.org/

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

  git send-email \
    --in-reply-to=CAA93jw6PN2nmgg3An-xkxc0bXxG+qV2k29oHRO14xB_y5DCAhg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=dave@taht.net \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    /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