From: Erik Auerswald <auerswal@unix-ag.uni-kl.de>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] where home 5G can go south
Date: Sat, 29 Oct 2022 11:40:23 +0200 [thread overview]
Message-ID: <523c300f-b2da-e2ff-f80b-2138e8263e61@unix-ag.uni-kl.de> (raw)
In-Reply-To: <B078ECBA-9A20-49B1-854E-8A31D7174720@jonathanfoulkes.com>
Hi,
On 28.10.22 23:10, jf--- via Bloat wrote:
>> On Oct 27, 2022, at 11:37 PM, Dave Taht via Bloat <bloat@lists.bufferbloat.net> wrote:
>>
>> https://blog.networkprofile.org/redundant-wan-ditching-t-mobile-5g-for-verizon-5g/
>>
>> This had some details as to the things that could go wrong from an
>> initial happy install of t-mobile, to something terrible.
>>
> We’ve observed growing variability on some TMHI setups from our fleet, and it seems there is a correlation to usage growth on a single tower. Seems neighbors talk to hear other after all ;-)
>
> And yes, horrible bufferbloat on these variable capacity links.
>
>> The author switched to verizon, but what guarantees of continued
>> reliability does one have?
>
> It seems none ATM, as it really depends on user density vs tower capacity. Woe to those that share a tower with a busy highway, ‘rush hour’ likely means low capacity and even higher latencies.
As another anecdote:
In the German I city where I live, Internet access via 4G usually
works well, even though there are noticeable bufferbloat effects
for those who know how to look.
But when there is a significantly higher number of mobile users,
e.g., because of a soccer game or some other event with large
attendance, latency goes up and reaches several seconds with just
light network usage.
Thanks,
Erik
next prev parent reply other threads:[~2022-10-29 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 3:37 Dave Taht
2022-10-28 21:10 ` jf
2022-10-29 9:40 ` Erik Auerswald [this message]
2022-10-29 16:51 ` Sebastian Moeller
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=523c300f-b2da-e2ff-f80b-2138e8263e61@unix-ag.uni-kl.de \
--to=auerswal@unix-ag.uni-kl.de \
--cc=bloat@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