General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Narseo Vallina Rodriguez <narseo@icsi.berkeley.edu>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Kartik Agaram <ak@akkartik.com>,
	Jordan Peacock <hewhocutsdown@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] http/2
Date: Thu, 12 Mar 2015 12:28:11 -0700	[thread overview]
Message-ID: <CAJmR=QmZyWhU+DVTnuO+eTepb3dEJ9K++Lbzs3Z270eO=qbV_g@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE3TSKMTTteBB7Qx8fpQfUpvd=WbE-P9CM0Ow98xcWSzKQ@mail.gmail.com>

> Tell me: does a Nokia E70 support fast dormancy? And how does a less than 2
> second setup latency translate into a 45 seconds latency under continuous
> load with continuous, smooth packet delivery? Which evaporates to half a
> second if I clamp the TCP receive window down to a sane value?
>

Well, I'm not saying that you're not right.

I'm just saying that there are many more dynamics that you cannot
control at the control-plane as they are transparent to the handset.

In the particular case you're describing, it's very likely a buffer
issue but it could be also a network issue as you could be connected
through an old APN (gateway). The E70 does not have fast dormancy, and
it does not support HSPA. It's a basic UMTS phone from 2005 which is
not very representative as of today.

The latency you're describing could be caused by signaling overload or
poor radio conditions but also very likely by buffers as you pointed.
Are there any other buffers on the RIL interface of the handset? How
do they behave? I know some operators use leaky bucket.

In any case, I was referring to a general scenario and as you framed
it initially "first packet", DNS, etc, it sounded as a control-plane
case. That's why I said in the previous email that I was not sure if
we're on the same page.

  reply	other threads:[~2015-03-12 19:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 21:38 Kartik Agaram
2015-03-12 15:02 ` Jonathan Morton
2015-03-12 18:18   ` Narseo Vallina Rodriguez
2015-03-12 18:39     ` Jonathan Morton
2015-03-12 18:56       ` Narseo Vallina Rodriguez
2015-03-12 19:07         ` Jonathan Morton
2015-03-12 19:28           ` Narseo Vallina Rodriguez [this message]
2015-03-12 19:42             ` Jonathan Morton
2015-03-15  7:23         ` Mikael Abrahamsson
2015-03-12 18:05 ` Rich Brown
2015-03-15  7:13 ` David Lang

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='CAJmR=QmZyWhU+DVTnuO+eTepb3dEJ9K++Lbzs3Z270eO=qbV_g@mail.gmail.com' \
    --to=narseo@icsi.berkeley.edu \
    --cc=ak@akkartik.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=hewhocutsdown@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