From: Dave Taht <dave.taht@gmail.com>
To: Joerg Deutschmann <joerg.deutschmann@fau.de>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] The NetEm qdisc does not work in conjunction with other qdiscs
Date: Fri, 25 Oct 2024 12:41:02 -0700 [thread overview]
Message-ID: <CAA93jw7_PoRHEHVoT66d990m7dOvyFPAM=V3i-Bdz8CB5Xq0SQ@mail.gmail.com> (raw)
In-Reply-To: <98eeb4b3-a8f8-4875-b021-aab0d5336959@fau.de>
[-- Attachment #1: Type: text/plain, Size: 2250 bytes --]
What I would typically do is setup netem on an inbound qdisc and whatever
is under test on the outbound.
even then, care is needed to ensure netem itself is not the bottleneck, has
an appropriate packet limit (I use millions), and that you are not running
out of cpu. For example it is really hard to pull 4gbit on cheap hw with
default qdiscs.
On Fri, Oct 25, 2024 at 11:54 AM Joerg Deutschmann via Bloat <
bloat@lists.bufferbloat.net> wrote:
> Dear all,
>
> bringing up again the question from a previous message to this list...
>
>
> https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel/#the-netem-qdisc-does-not-work-in-conjunction-with-other-qdiscs
> says to not use NetEm together with other qdiscs.
>
> Is this still true?
>
> How could one emulate bottlenecks together with fq_codel?
>
> Best regards
> Joerg
>
>
> On 15.01.24 13:24, O. P. via Bloat wrote:
> >
> > Hi there,
> >
> > I'm trying to set up a testbed to evaluate different AQM techniques
> > using docker containers.
> > My first idea to create congestion was to use netem. However I later
> > came across
> >
> https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel/
> <
> https://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_Codel/>
> which discourages using netem. Since the document is from 2014 and also
> states that "netem has been improving", my question was wether the current
> netem has improved sufficiently to be used to get realistic results.
> > If netem has improved sufficienly, what would be the correct way to use
> > netem along fq, fq-codel or codel for example ?
> > If not, is HTB still the best way to perform rate limiting ? Is there a
> > prefered way to combine HTB with AQMs ?
> >
> > Best regards
> >
> > John
> >
> > _______________________________________________
> > Bloat mailing list
> > Bloat@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
--
Dave Täht CSO, LibreQos
[-- Attachment #2: Type: text/html, Size: 3680 bytes --]
next prev parent reply other threads:[~2024-10-25 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 12:24 [Bloat] Testbed using containers O. P.
2024-10-25 18:54 ` [Bloat] The NetEm qdisc does not work in conjunction with other qdiscs Joerg Deutschmann
2024-10-25 19:41 ` Dave Taht [this message]
2024-10-25 22:33 ` Joerg Deutschmann
2024-10-25 19:55 ` Maximilian Bachl
2024-10-25 21:02 ` Stephen Hemminger
2024-10-25 22:47 ` Joerg Deutschmann
2024-10-25 23:12 ` Dave Taht
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7_PoRHEHVoT66d990m7dOvyFPAM=V3i-Bdz8CB5Xq0SQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=joerg.deutschmann@fau.de \
/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