From: Bob McMahon <bob.mcmahon@broadcom.com>
To: "Livingood, Jason" <jason_livingood@comcast.com>
Cc: Rich Brown <richb.hanover@gmail.com>,
"make-wifi-fast@lists.bufferbloat.net"
<make-wifi-fast@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Make-wifi-fast] Looking for a citation...
Date: Mon, 19 Aug 2024 15:12:36 -0700 [thread overview]
Message-ID: <CAHb6LvoGvfZ3Cbby5FmefTpJys=FrAFBt8KRSzLBsSaDX2tqsA@mail.gmail.com> (raw)
In-Reply-To: <00D0FC8B-AC22-43DE-80F5-E86A786D15EA@comcast.com>
[-- Attachment #1.1: Type: text/plain, Size: 5166 bytes --]
> for users with access links that exceed 800~Mbps, the user's home
wireless network was the performance bottleneck 100% of the time.
hmm, I'm concerned about a study that has a 100% number.
I have a home Wi-Fi infrastructure and a >1G xfinity plan. I don't have a
Wi-Fi bottleneck because I use a 2.5G wired fronhaul with a 4 port
proteclli vault pro connected to 4 Wi-Fi 6e APs that are located properly
per spacetime. I didn't need to consult with anybody nor get others
agreements to do this. As a homeowner, I did it all by myself. Wi-Fi has
never been the problem since doing this despite the 100% claim.
I treat communications like an essential service. I don't run all my
electrical devices from one single extension cord. Probably time for
homeowners to think about updating their comm infra and treat it as if it's
a critical service because it is.
Bob
On Mon, Aug 19, 2024 at 6:29 AM Livingood, Jason via Make-wifi-fast <
make-wifi-fast@lists.bufferbloat.net> wrote:
> See https://arxiv.org/abs/2311.05499 and the refs at the end as well for
> prior studies.
>
>
> Measuring the Prevalence of WiFi Bottlenecks in Home Access Networks
>
> Ranya Sharma, Marc Richardson, Guilherme Martins, Nick Feamster
>
> As broadband Internet speeds continue to increase, the home wireless
> ("WiFi") network may more frequently become a performance bottleneck. Past
> research, now nearly a decade old, initially documented this phenomenon
> through indirect inference techniques, noting the prevalence of WiFi
> bottlenecks but never directly measuring them. In the intervening years,
> access network (and WiFi) speeds have increased, warranting a re-appraisal
> of this important question, particularly with renewed private and federal
> investment in access network infrastructure. This paper studies this
> question, developing a new system and measurement technique to perform
> direct measurements of WiFi and access network performance, ultimately
> collecting and analyzing a first-of-its-kind dataset of more than 13,000
> joint measurements of WiFi and access network throughputs, in a real-world
> deployment spanning more than 50 homes, for nearly two years. Using this
> dataset, we re-examine the question of whether, when, and to what extent a
> user's home wireless network may be a performance bottleneck, particularly
> relative to their access connection. We do so by directly and continuously
> measuring the user's Internet performance along two separate components of
> the Internet path -- from a wireless client inside the home network to the
> wired point of access (e.g., the cable modem), and from the wired point of
> access to the user's ISP. Confirming and revising results from more than a
> decade ago, we find that a user's home wireless network is often the
> throughput bottleneck. In particular, for users with access links that
> exceed 800~Mbps, the user's home wireless network was the performance
> bottleneck 100% of the time.
>
> On 8/18/24, 05:08, "Bloat on behalf of Rich Brown 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:
>
>
> In various posts, I have baldly asserted that "above 300-500mbps ISP
> links, all the bufferbloat moves into the Wi-Fi."
>
>
> I am pretty sure that I someone on these lists stated that as fact.
>
>
> Could I get a link to a discussion that is definitive? Or a statement that
> is actually true that I can incorporate into my future posts? Many thanks.
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net <mailto:Bloat@lists.bufferbloat.net>
>
> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!Hx6KOEdA33LoKQOuNmwKNbenbWB3x_uE0dpwptAGKVkIPym66koG6UHe8M0F4nLSAou42YEvAlZm9ctVKh8AMdt0daaYlQ$
> <
> https://urldefense.com/v3/__https://lists.bufferbloat.net/listinfo/bloat__;!!CQl3mcHX2A!Hx6KOEdA33LoKQOuNmwKNbenbWB3x_uE0dpwptAGKVkIPym66koG6UHe8M0F4nLSAou42YEvAlZm9ctVKh8AMdt0daaYlQ$>
>
>
>
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #1.2: Type: text/html, Size: 6735 bytes --]
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
prev parent reply other threads:[~2024-08-19 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 9:08 [Bloat] " Rich Brown
2024-08-18 15:32 ` Jan Ceuleers
2024-08-18 15:47 ` Dave Taht
2024-08-18 16:01 ` David Lang
2024-08-18 16:12 ` Dave Taht
2024-08-18 18:43 ` dan
2024-08-18 18:48 ` [Bloat] [Make-wifi-fast] " Sebastian Moeller
2024-08-18 18:52 ` David Lang
2024-08-19 13:29 ` [Bloat] " Livingood, Jason
2024-08-19 22:12 ` Bob McMahon [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHb6LvoGvfZ3Cbby5FmefTpJys=FrAFBt8KRSzLBsSaDX2tqsA@mail.gmail.com' \
--to=bob.mcmahon@broadcom.com \
--cc=bloat@lists.bufferbloat.net \
--cc=jason_livingood@comcast.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=richb.hanover@gmail.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