General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>,
	Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Subject: Re: [Bloat] ookla speedtests on 5G
Date: Tue, 9 May 2023 05:59:31 +0000	[thread overview]
Message-ID: <AM8PR07MB813764D61632487274197E00C2769@AM8PR07MB8137.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <CAA93jw4FqRQN+hMW5VacNtpVRfhmyzpfd5pyiJuqRPwtp8aKyA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3105 bytes --]

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@gmail.com>
Sent: Monday, 8 May 2023 21:17
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Cc: bloat@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@lists.bufferbloat.net<mailto:bloat@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@gmail.com<mailto:dave.taht@gmail.com>>
> To: Rpm <rpm@lists.bufferbloat.net<mailto:rpm@lists.bufferbloat.net>>, bloat
>       <bloat@lists.bufferbloat.net<mailto:bloat@lists.bufferbloat.net>>,  libreqos
>       <libreqos@lists.bufferbloat.net<mailto:libreqos@lists.bufferbloat.net>>
> Subject: [Bloat] ookla speedtests on 5G
> Message-ID:
>       <CAA93jw5gM3ujEemMjJv81vxSpKigZBJO64g7J6TKBJxXK93fsQ@mail.gmail.com<mailto:CAA93jw5gM3ujEemMjJv81vxSpKigZBJO64g7J6TKBJxXK93fsQ@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@lists.bufferbloat.net<mailto:Bloat@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

[-- Attachment #2: Type: text/html, Size: 8186 bytes --]

  reply	other threads:[~2023-05-09  5:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.9.1683216001.4349.bloat@lists.bufferbloat.net>
2023-05-05 13:55 ` Ingemar Johansson S
2023-05-08 19:16   ` Dave Taht
2023-05-09  5:59     ` Ingemar Johansson S [this message]
2023-05-04  1:32 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/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=AM8PR07MB813764D61632487274197E00C2769@AM8PR07MB8137.eurprd07.prod.outlook.com \
    --to=ingemar.s.johansson@ericsson.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@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