From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: Mikael Abrahamsson <swmike@swm.pp.se>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] T-Mobile LTE buffer bloat
Date: Thu, 31 Oct 2013 08:43:20 +0000 [thread overview]
Message-ID: <82AB329A76E2484D934BBCA77E9F524963829BA1@PALLENE.office.hd> (raw)
In-Reply-To: <alpine.DEB.2.02.1310310100050.1838@uplift.swm.pp.se>
Also, it would be important to understand what radio access technology the LTE-WiFi-GW was really using at the time of the measurement. In hybrid GSM/UMTS/LTE networks (like T-Mobile's), mobile phones frequently fall back to GSM (GPRS), so you cannot blame LTE in this case.
There are many myths around bufferbloat in mobile networks. You really need to understand the specifics of the network, its utilization at a given time -- and the deficiencies of the gear you are using.
Having said that, in LTE there are apparently significant differences in latency (variation) depending on the operator and equipment vendor. For example, I have seen LTE measurements from hotspot areas in Tokyo that still looked much better (max 60 ms uplink delay) than what I hear sometimes from friends in the US.
It's about time for structured measurement campaign that helps us to analyze this better.
Best regards,
Dirk
> -----Original Message-----
> From: bloat-bounces@lists.bufferbloat.net [mailto:bloat-
> bounces@lists.bufferbloat.net] On Behalf Of Mikael Abrahamsson
> Sent: Donnerstag, 31. Oktober 2013 01:02
> To: Stephen Hemminger
> Cc: bloat@lists.bufferbloat.net
> Subject: Re: [Bloat] T-Mobile LTE buffer bloat
>
> On Wed, 30 Oct 2013, Stephen Hemminger wrote:
>
> > There is zero configuration of proxy, it is just a LTE <-> wifi hotspot.
> > I suspect some caching (or commercial interest) at their end.
>
> I have no insight in how T-Moble does things, but I know that vendors pitch
> video/image compression stuff and you want to put it *before* it goes out
> the radio network (because that's the expensive resource), so that's why my
> guess it's doing the image-rewriting not in the end user box, but in a centrally
> placed device in their network.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2013-10-31 8:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 23:25 Stephen Hemminger
2013-10-30 23:34 ` Mikael Abrahamsson
2013-10-30 23:35 ` Dave Taht
2013-10-31 0:29 ` Srikanth Sundaresan
2013-10-30 23:57 ` Stephen Hemminger
2013-10-31 0:02 ` Mikael Abrahamsson
2013-10-31 8:43 ` Dirk Kutscher [this message]
2013-10-31 0:24 ` Michael Richardson
2013-10-31 0:26 ` Mikael Abrahamsson
2013-10-31 2:04 ` Stefan Alfredsson
2013-10-31 2:32 ` Dave Taht
2013-10-31 12:27 ` [Bloat] mobile broadband " Stefan Alfredsson
2013-11-01 1:09 ` Dave Taht
2013-11-01 1:32 ` Dave Taht
2013-11-01 1:39 ` Dave Taht
2013-11-01 12:48 ` Mikael Abrahamsson
2013-11-01 20:22 ` Aaron Wood
2013-11-01 20:29 ` Jonathan Morton
2013-11-02 16:41 ` Mikael Abrahamsson
2013-10-31 5:45 [Bloat] T-Mobile LTE " Hal Murray
2013-11-01 14:36 ` Jim Gettys
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=82AB329A76E2484D934BBCA77E9F524963829BA1@PALLENE.office.hd \
--to=dirk.kutscher@neclab.eu \
--cc=bloat@lists.bufferbloat.net \
--cc=stephen@networkplumber.org \
--cc=swmike@swm.pp.se \
/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