From: "Luis A. Cornejo" <luis.a.cornejo@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Jay Moran <jay@tp.org>, Cake List <cake@lists.bufferbloat.net>,
IETF IPPM WG <ippm@ietf.org>, "MORTON JR.,
AL" <acmorton@att.com>, Rpm <rpm@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
dickroy@alum.mit.edu, libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] [Bloat] [Rpm] [Starlink] the grinch meets cloudflare'schristmas present
Date: Thu, 12 Jan 2023 10:20:09 -0600 [thread overview]
Message-ID: <CAKJdXWCiws8Hg8crk6Abh4wjwOKTvO5neQvZR4tt4goVOHhQdQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4DcBhA8CevRQoMbzjO-3Jt+emr+xvnJ-hUGkT+n0KJzg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 707 bytes --]
I have noticed that in the AM things tend to be much more acceptable. I'll
see what I can do for a PM run, anecdotally it seems from 5 p.m - 10:30
p.m. the bandwidth definitely drops closer to 50/3 avg and the latency
suffers as well, but not as bad as it used to be, so it is reliably better
for me, but I am in a fairly rural cell in Walker Co. Tx, but then again
there is a lot of rural Texans. Meanwhile, here is another cloudflare run
and a waveform one too:
https://www.waveform.com/tools/bufferbloat?test-id=daeaefc6-23fe-43d8-9826-210cfb381f05
On Thu, Jan 12, 2023 at 10:12 AM Dave Taht <dave.taht@gmail.com> wrote:
> Either starlink has vastly improved, or the test is way off in this case.
>
[-- Attachment #1.2: Type: text/html, Size: 1156 bytes --]
[-- Attachment #2: Web capture_12-1-2023_101327_speed.cloudflare.com.jpeg --]
[-- Type: image/jpeg, Size: 219644 bytes --]
next prev parent reply other threads:[~2023-01-12 16:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 17:26 [LibreQoS] the grinch meets cloudflare's christmas present Dave Taht
2023-01-04 19:20 ` [LibreQoS] [Rpm] " jf
2023-01-04 20:02 ` rjmcmahon
2023-01-05 11:11 ` [LibreQoS] [Bloat] " Sebastian Moeller
2023-01-06 0:30 ` [LibreQoS] [Starlink] [Bloat] [Rpm] the grinch meets cloudflare'schristmas present Dick Roy
2023-01-06 2:33 ` rjmcmahon
2023-01-06 9:55 ` Sebastian Moeller
2023-01-05 4:25 ` [LibreQoS] [Starlink] [Rpm] the grinch meets cloudflare's christmas present Dick Roy
2023-01-06 16:38 ` [LibreQoS] " MORTON JR., AL
2023-01-06 20:38 ` [LibreQoS] [Rpm] " rjmcmahon
2023-01-06 20:47 ` rjmcmahon
2023-01-06 23:29 ` [LibreQoS] [Starlink] [Rpm] the grinch meets cloudflare'schristmas present Dick Roy
2023-01-06 23:44 ` rjmcmahon
2023-01-07 0:31 ` Dick Roy
2023-01-10 17:24 ` [LibreQoS] [Bloat] " Luis A. Cornejo
2023-01-11 5:07 ` [LibreQoS] [Rpm] [Bloat] [Starlink] " Dave Taht
2023-01-11 11:05 ` [LibreQoS] [Bloat] [Rpm] " Jay Moran
2023-01-12 16:01 ` Luis A. Cornejo
2023-01-12 16:12 ` Dave Taht
2023-01-12 16:20 ` Luis A. Cornejo [this message]
2023-01-12 17:42 ` MORTON JR., AL
2023-01-13 3:28 ` Luis A. Cornejo
2023-01-13 3:47 ` Luis A. Cornejo
2023-01-13 4:01 ` Dave Taht
2023-01-13 14:08 ` Luis A. Cornejo
2023-01-13 3:30 ` Luis A. Cornejo
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=CAKJdXWCiws8Hg8crk6Abh4wjwOKTvO5neQvZR4tt4goVOHhQdQ@mail.gmail.com \
--to=luis.a.cornejo@gmail.com \
--cc=acmorton@att.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=dickroy@alum.mit.edu \
--cc=ippm@ietf.org \
--cc=jay@tp.org \
--cc=libreqos@lists.bufferbloat.net \
--cc=rpm@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