From: dan <dandenson@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: libreqos <libreqos@lists.bufferbloat.net>
Subject: Re: [LibreQoS] monitoring twitter rtt looks useful
Date: Sun, 13 Nov 2022 15:49:51 -0700 [thread overview]
Message-ID: <CAA_JP8Xu_ayfqhOzxky+kkz=eHz-qNp8fjpGNOy5Ssy9gmc8bQ@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4NOz06zSHD=jZv3b8ETLM5ZGwxQr53S76b4Sd6V+KJhw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1495 bytes --]
It's pretty interesting and though they were 'surprised' at the results, as
someone who lives 'a lot' of hops from major datacenters this makes perfect
sense lol.
Here's a local Spectrum circuit to twitter:
[image: Screenshot 2022-11-13 at 3.45.00 PM.png]
and here's off one of my Lumen fiber circuits:
[image: Screenshot 2022-11-13 at 3.45.19 PM.png]
41ms is 'fine'... except this is about the best it gets here to a major
service that lives in tons of datacenters off a DIA 10G fiber circuit.
104.244.42.65/.1 are the two DNS records I get for twitter and have the
same numbers between them.
Also, not to 'brag' here but I'm rocking that solid 41ms and the furthest
edges of my network are 15ms out so my wISP service spanks Spectrum in
latency every time. Also note that the 41ms is through a cake shaper at a
site that is passing about 1600x200Mbps right now.
On Sun, Nov 13, 2022 at 2:43 PM Dave Taht via LibreQoS <
libreqos@lists.bufferbloat.net> wrote:
> If we only knew which 100 ips it was.
>
>
> https://blog.twitter.com/engineering/en_us/topics/infrastructure/2019/expand-the-edge
>
> --
> 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
> _______________________________________________
> LibreQoS mailing list
> LibreQoS@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/libreqos
>
[-- Attachment #1.2: Type: text/html, Size: 2460 bytes --]
[-- Attachment #2: Screenshot 2022-11-13 at 3.45.00 PM.png --]
[-- Type: image/png, Size: 23231 bytes --]
[-- Attachment #3: Screenshot 2022-11-13 at 3.45.19 PM.png --]
[-- Type: image/png, Size: 20086 bytes --]
next prev parent reply other threads:[~2022-11-13 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 21:43 Dave Taht
2022-11-13 22:49 ` dan [this message]
2022-11-13 23:24 ` 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/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='CAA_JP8Xu_ayfqhOzxky+kkz=eHz-qNp8fjpGNOy5Ssy9gmc8bQ@mail.gmail.com' \
--to=dandenson@gmail.com \
--cc=dave.taht@gmail.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