From: Dave Taht <dave.taht@gmail.com>
To: "MORTON JR., AL" <acmorton@att.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] the k8 hairball
Date: Mon, 21 Nov 2022 08:42:14 -0800 [thread overview]
Message-ID: <CAA93jw6wNNdTp8up2VRD3=fxgzDB=dE15ZdGVsea_TwwoqH5Fw@mail.gmail.com> (raw)
In-Reply-To: <CH0PR02MB7980EAA59DA07E1CBBD8DBC8D30A9@CH0PR02MB7980.namprd02.prod.outlook.com>
On Mon, Nov 21, 2022 at 5:44 AM MORTON JR., AL <acmorton@att.com> wrote:
>
> I'll take that bet, Dave, because I'm sure it mentions Throughput (and I only looked at part of the web page). It wouldn't be benchmarking without some definition of Throughput...
Nope. Not mentioned once. I shoulda hung an amount on that bet. Also,
I was overly vague, I'd meant latency or latency under load...
I have no idea why the k8 crowd thinks the network stack isn't
something to worry about...
>
> Full Disclosure: I have seen an earlier K8s benchmarking study, it could be related work. Among those of us who discussed the findings, one "knock" was that they only tested with TCP streams. Benchmarking for RFC 2544 Throughput requires UDP streams, no TCP flow-control complexities...
>
> Al
>
> > -----Original Message-----
> > From: LibreQoS <libreqos-bounces@lists.bufferbloat.net> On Behalf Of Dave Taht
> > via LibreQoS
> > Sent: Sunday, November 20, 2022 9:28 PM
> > To: libreqos <libreqos@lists.bufferbloat.net>
> > Subject: [LibreQoS] the k8 hairball
> >
> > without reading this, I am willing to offer 3x1 odds this report does
> > not mention one specific tcp related metric.
> >
> > https://urldefense.com/v3/__https://humanitec.com/whitepapers/kubernetes-
> > benchmarking-study-2022__;!!BhdT!gy_08-Lw3wEiAgdspSMpcAGcLbfMq-my_-
> > YYi47om7KKd1gPKSdrT6L3o95U3sYPPpciDoMZMouCUh54K8qkmxM$
> >
> > Any takers?
> >
> > --
> > This song goes out to all the folk that thought Stadia would work:
> > https://urldefense.com/v3/__https://www.linkedin.com/posts/dtaht_the-mushroom-
> > song-activity-6981366665607352320-FXtz__;!!BhdT!gy_08-Lw3wEiAgdspSMpcAGcLbfMq-
> > my_-YYi47om7KKd1gPKSdrT6L3o95U3sYPPpciDoMZMouCUh54RS9Rq-c$
> > Dave Täht CEO, TekLibre, LLC
> > _______________________________________________
> > LibreQoS mailing list
> > LibreQoS@lists.bufferbloat.net
> > https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/libreqos__;
> > !!BhdT!gy_08-Lw3wEiAgdspSMpcAGcLbfMq-my_-
> > YYi47om7KKd1gPKSdrT6L3o95U3sYPPpciDoMZMouCUh54XdGMIEA$
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
prev parent reply other threads:[~2022-11-21 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 2:27 Dave Taht
2022-11-21 13:43 ` MORTON JR., AL
2022-11-21 16:42 ` Dave Taht [this message]
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6wNNdTp8up2VRD3=fxgzDB=dE15ZdGVsea_TwwoqH5Fw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=acmorton@att.com \
--cc=libreqos@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