From: "Livingood, Jason" <jason_livingood@comcast.com>
To: David Lang <david@lang.hm>, "David P. Reed" <dpreed@deepplum.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] bbr vs all the aqms, cake winning...
Date: Mon, 30 Sep 2024 14:49:59 +0000 [thread overview]
Message-ID: <60269A01-BC45-4351-ABD2-2F10C2931C35@comcast.com> (raw)
In-Reply-To: <793rr84s-q113-npr2-21p0-4ror01s1p376@ynat.uz>
On 9/28/24, 21:35, "Bloat on behalf of David Lang via Bloat" <bloat-bounces@lists.bufferbloat.net <mailto:bloat-bounces@lists.bufferbloat.net> on behalf of bloat@lists.bufferbloat.net <mailto:bloat@lists.bufferbloat.net>> wrote:
> That's why I was saying 'traffic simulator' rather than 'traffic replay'. A good
simulator is a much harder problem
[JL] Further to David R's point - there is so much variation in client, device, home network, CPE, etc. that simulation just never catches all the corner cases (and so IMO not worth the time investment in most cases). That's why in my experience large operators of networks and applications will of course run automatic QA tests in a lab, but quickly move on to phased deployment - with a gradually expanded deployment that is coupled with alerting for changes in operations patterns/performance/etc.
next prev parent reply other threads:[~2024-09-30 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 22:21 [Cake] " Dave Taht
2024-09-27 21:10 ` David P. Reed
2024-09-27 21:43 ` David Lang
2024-09-28 21:07 ` David P. Reed
2024-09-29 1:35 ` David Lang
2024-09-30 14:49 ` Livingood, Jason [this message]
2024-09-30 14:47 ` [Cake] [Bloat] " Juliusz Chroboczek
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=60269A01-BC45-4351-ABD2-2F10C2931C35@comcast.com \
--to=jason_livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=david@lang.hm \
--cc=dpreed@deepplum.com \
/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