W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2014

Re: Reference set in HPACK

From: Greg Wilkins <gregw@intalio.com>
Date: Wed, 2 Jul 2014 09:37:23 +0200
Message-ID: <CAH_y2NHJFQA-nLN9bw9wwVhLAhcY0ABXNQL9yCC5OGR-Y5_dzw@mail.gmail.com>
To: Roberto Peon <grmocg@gmail.com>
Cc: Kazu Yamamoto <kazu@iij.ad.jp>, HTTP Working Group <ietf-http-wg@w3.org>
On 2 July 2014 08:09, Roberto Peon <grmocg@gmail.com> wrote:

> Even a few bytes per request adds up as the number of requests go up.
> Lets think about a page today that has 100 elements, which is something we
> see today.
> If the headers were regularized, with the use of a reference set, one
> could imagine a reduction of 20 bytes per header.
> With 100 elements, this is approximately 2k of data, or two packets worth.
>

Roberto,

I think this kind of calculation needs some real data.     Maintaining a
reference set is not a zero byte deal, as it still requires bytes to be
sent to remove entries from the reference set that are not needed.  If real
data shows that removals are frequent, then they may add up to close to the
2k also.

I don't think that it is unreasonable to request that realistic data is
provided to prove that a reference set is worthwhile.   It  would be good
to obtain and evaluate such data for both a single connection and coalesced
connections.

regards








-- 
Greg Wilkins <gregw@intalio.com>
http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales
http://www.webtide.com  advice and support for jetty and cometd.
Received on Wednesday, 2 July 2014 07:37:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 09:57:08 UTC