Lets make wifi fast again!
 help / color / mirror / Atom feed
From: "Livingood, Jason" <jason_livingood@comcast.com>
To: 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: [Make-wifi-fast] [Bloat] Looking for a citation...
Date: Mon, 19 Aug 2024 13:29:16 +0000	[thread overview]
Message-ID: <00D0FC8B-AC22-43DE-80F5-E86A786D15EA@comcast.com> (raw)
In-Reply-To: <93639364-6937-4EE6-B218-2A02AF212362@gmail.com>

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$> 




  parent reply	other threads:[~2024-08-19 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18  9:08 [Make-wifi-fast] " Rich Brown
2024-08-18 18:48 ` Sebastian Moeller
2024-08-18 18:52   ` [Make-wifi-fast] [Bloat] " David Lang
2024-08-19 13:29 ` Livingood, Jason [this message]
2024-08-19 22:12   ` Bob McMahon

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/make-wifi-fast.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=00D0FC8B-AC22-43DE-80F5-E86A786D15EA@comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=bloat@lists.bufferbloat.net \
    --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