From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 073163CB5F for ; Mon, 13 Mar 2023 15:52:18 -0400 (EDT) Received: by mail-yb1-xb2a.google.com with SMTP id r1so515231ybu.5 for ; Mon, 13 Mar 2023 12:52:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aterlo.com; s=google; t=1678737138; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=bBgGpdTWSFs0fTKF4O+tUQ+9h5j3Kq+x+lRatGZJlcE=; b=cBQFpfYGSvh/bwuz6B+YtsAg0PZ1BM1/JgkkPJsWUYuN44ToP5wdMJUa2SdGxmKnRM l2dHMAUC/5M73o3lCQdsOXtfFCviMn3CZkcEya1ltnE7fpCwUHT3r7vdvdtN4IF6/75/ cFbQin3sAaJlQuQjUxbXQNGUHA8u7+wQu2ziQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678737138; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=bBgGpdTWSFs0fTKF4O+tUQ+9h5j3Kq+x+lRatGZJlcE=; b=SykVk3C3G3W1S/HFAUiHkP5fsvs61xE1zcmr63wNjqRnTFPk0iQkGEhrtx3nJbVV/x BcR3T1YEcCnFrCjnOaspS2qlliSRZ8hmhp7aW6yTpnCzlJ0z38rq3pRuIeGEqU0jP1yH RH09iD/Y9IxRhdvsMO1RvEqVzAidfz8PAQOXMYPOE06EMtmINBd3qvjXiBpd02pkiP1G PdQEQtEx6T/f+XSXGfgQuYMAriK1QK8I84GcdZXEbXnpT92m3o0jxnUiztPbnWBUzg5L XaPL9JSWjWSAPnr+dJ/racEW7UXEC5ogyvHY+/NAr+G1SpM1fPY1tyaJJnC04ZNPRxn/ P2MQ== X-Gm-Message-State: AO0yUKUOn0Ym4F2tuJ6ZN5yBJ2Sm5ijaIYA0Tk/JRDq6QskNoHZRPul3 WW0LGH/wW0P4xHGeI6nTOoLD1oDNQ2p7dzTfRP+1fA== X-Google-Smtp-Source: AK7set/RadZNJFNsnfKbaHQyryRCdoC46bbz50NBn785AoxB3Ptz/6XS77JHdRyyRxX73M2ZZ6BkKw8oX+daIpSMowk= X-Received: by 2002:a05:6902:282:b0:a02:a3a6:7a67 with SMTP id v2-20020a056902028200b00a02a3a67a67mr21925607ybh.11.1678737138212; Mon, 13 Mar 2023 12:52:18 -0700 (PDT) MIME-Version: 1.0 References: <1672786712.106922180@apps.rackspace.com> <77CCAD19-07E0-4F9E-88C1-D207CF7BF376@cable.comcast.com> <83ffc0dad19e3343e49271889369cefc@rjmcmahon.com> <3CD0B9E6-0B2A-4A70-8F53-ED0822DF77A6@gmx.de> <13DE6E53-665F-4C20-BBE2-70E685421E9D@gmx.de> <22C819FA-DDD7-4B9B-8C09-8008D4273287@gmx.de> In-Reply-To: From: Jeremy Austin Date: Mon, 13 Mar 2023 12:52:07 -0700 Message-ID: To: dan Cc: Sebastian Moeller , Rpm , libreqos , Dave Taht via Starlink , rjmcmahon , bloat Content-Type: multipart/alternative; boundary="000000000000cb73e905f6cd7268" Subject: Re: [Starlink] [Rpm] [LibreQoS] [EXTERNAL] Re: Researchers Seeking Probe Volunteers in USA X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2023 19:52:19 -0000 --000000000000cb73e905f6cd7268 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 13, 2023 at 12:34=E2=80=AFPM dan wrote: > > See, you're coming around. Cake is autorating (or very close, 'on > device') at the wan port. not the speed test device or software. And > the accurate data is collected by cake, not the speed test tool. That > tool is reporting false information because it must, it doesn't know > the other consumers on the network. It's 'truest' when the network is > quiet but the more talkers the more the tool lies. > > cake, the kernel, and the wan port all have real info, the speed test > tool does not. > I'm running a bit behind on commenting on the thread (apologies, more later) but I point you back at my statement about NTIA (and, to a certain extent, the FCC): Consumers use speed tests to qualify their connection. Whether AQM is applied or not, a speed test does not reflect in all circumstances the capacity of the pipe. One might argue that it seldom reflects it. Unfortunately, those who have "real info", to use Dan's term, are currently nearly powerless to use it. I am, if possible, on both the ISP and consumer side here. And yes, Preseem does have an iron in this fire, or at least a dog in this fight. Ironically, the FCC testing for CAF/RDOF actually *does* take interface load into account, only tests during peak busy hours, and /then/ does a speed test. But NTIA largely ignores that for BEAD. --=20 -- Jeremy Austin Sr. Product Manager Preseem | Aterlo Networks preseem.com Book a Call: https://app.hubspot.com/meetings/jeremy548 Phone: 1-833-733-7336 x718 Email: jeremy@preseem.com Stay Connected with Newsletters & More: *https://preseem.com/stay-connected/* --000000000000cb73e905f6cd7268 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Mar 13, 2023 at 12:34=E2=80= =AFPM dan <dandenson@gmail.com> wrote:

See, you're coming around.=C2=A0 Cake is autorating (or very close, = 9;on
device') at the wan port.=C2=A0 not the speed test device or software.= =C2=A0 And
the accurate data is collected by cake, not the speed test tool.=C2=A0 That=
tool is reporting false information because it must, it doesn't know the other consumers on the network.=C2=A0 It's 'truest' when th= e network is
quiet but the more talkers the more the tool lies.

cake, the kernel, and the wan port all have real info, the speed test
tool does not.

I'm running a bit behind on c= ommenting on the thread (apologies, more later) but I point you back at my = statement about NTIA (and, to a certain extent, the FCC):=C2=A0
<= br>
Consumers use speed tests to qualify their connection.
<= div>

--000000000000cb73e905f6cd7268--