From: Narseo Vallina Rodriguez <narseo@icsi.berkeley.edu>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Jordan Peacock <hewhocutsdown@gmail.com>,
Kartik Agaram <ak@akkartik.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] http/2
Date: Thu, 12 Mar 2015 11:18:09 -0700 [thread overview]
Message-ID: <CAJmR=Qm6xdX2gGq+cGM2awyDYJK+5t4-HpvRVHZ-Ng9AbNi64w@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE28yrYQEt8UMDZ6xTGOXbzXKY-a9BfQs3TOFPQ2KtyVgw@mail.gmail.com>
Hi Jonathan
> Status quo is that loading a web page with many resources on it is
> unreliable. Early connections succeed and become established, the congestion
> window opens, the buffer in the 3G tower begins to fill up, inducing several
> seconds of latency, and subsequent DNS lookups and TCP handshakes tend to
> time out. End result: often, half the images on the page are broken.
>
The way you're describing this specific part, sounds more to me like a
control-plane latency issue (i.e., the time for the RNC to allocate a
radio channel to the client by promoting it from IDLE/FACH to DCH)
rather than a buffer size related issue (which is actually introduced
both on the handset and the RNC/eNB to deal with the C-Plane latency)
https://www.qualcomm.com/media/documents/files/qualcomm-research-latency-in-hspa-data-networks.pdf
next prev parent reply other threads:[~2015-03-12 18:18 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 [this message]
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
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=Qm6xdX2gGq+cGM2awyDYJK+5t4-HpvRVHZ-Ng9AbNi64w@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