[Bloat] ookla speedtests on 5G

[Ingemar Johansson S]

Hi

I reacted mostly on the extremely low throughput in the top post in the twitter thread, it is possible that radio link failure caused a large amount of bloat in this case.
The amount of buffer bloat in 5G systems is quite vendor specific. So it is hard to give any good numbers what one can expect.
But sure, seconds of bloat is gross overkill and possible evidence that AQM is disabled. Typically the AQM on the network side handles the downlink traffic, while for the uplink traffic the AQM needs to be on the modem side.
L4S, which is being standardized in 3GPP can reduce bloat quite considerably, but one need to realize that L4S does perhaps not fit for all traffic.
See page 5 in https://datatracker.ietf.org/meeting/115/materials/slides-115-iccrg-5g-and-l4s-congestion-control-considerations-00


/Ingemar

From: Dave Taht <dave.taht at gmail.com>
Sent: Monday, 8 May 2023 21:17
To: Ingemar Johansson S <ingemar.s.johansson at ericsson.com>
Cc: bloat at lists.bufferbloat.net
Subject: Re: [Bloat] ookla speedtests on 5G



On Fri, May 5, 2023 at 6:55 AM Ingemar Johansson S via Bloat <bloat at lists.bufferbloat.net<mailto:bloat at lists.bufferbloat.net>> wrote:
1.08Mbps down and 0.33Mbps up is hardly representative for 5G.. I wonder if the measurement was done three stories down in a basement :-)

the twitter thread itself was a pretty representative example of how bad the bloat can get, even at the highest 5G speeds.

/Ingemar

>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 3 May 2023 18:32:56 -0700
> From: Dave Taht <dave.taht at gmail.com<mailto:dave.taht at gmail.com>>
> To: Rpm <rpm at lists.bufferbloat.net<mailto:rpm at lists.bufferbloat.net>>, bloat
>       <bloat at lists.bufferbloat.net<mailto:bloat at lists.bufferbloat.net>>,  libreqos
>       <libreqos at lists.bufferbloat.net<mailto:libreqos at lists.bufferbloat.net>>
> Subject: [Bloat] ookla speedtests on 5G
> Message-ID:
>       <CAA93jw5gM3ujEemMjJv81vxSpKigZBJO64g7J6TKBJxXK93fsQ at mail.gmail.com<mailto:CAA93jw5gM3ujEemMjJv81vxSpKigZBJO64g7J6TKBJxXK93fsQ at mail.gmail.com>
> >
> Content-Type: text/plain; charset="UTF-8"
>
> This was quite the long list of speedtest pics, all showing pretty
> gnarly bufferbloat across all services.
>
> https://twitter.com/ianzelbo/status/1653757825972142081
>
> Not a single poster caught on to the awfulness in the responsiveness
> numbers.
>
>
> --
> Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937
> /
> Dave Täht CSO, LibreQos
>
>
> ------------------------------

_______________________________________________
Bloat mailing list
Bloat at lists.bufferbloat.net<mailto:Bloat at lists.bufferbloat.net>
https://lists.bufferbloat.net/listinfo/bloat<https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-454445555731-5f070e024f500e6b&q=1&e=12b802be-c3ee-4da6-bc15-6d9b81605a53&u=https%3A%2F%2Flists.bufferbloat.net%2Flistinfo%2Fbloat>


--
Podcast: https://www.linkedin.com/feed/update/urn:li:activity:7058793910227111937/
Dave Täht CSO, LibreQos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20230509/d2e2d1fd/attachment-0001.html>