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

Re: Compression ratio of HPACK.

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Sat, 01 Feb 2014 06:24:20 +1300
Message-ID: <52EBDC44.2000909@treenet.co.nz>
To: ietf-http-wg@w3.org
On 1/02/2014 5:22 a.m., Jeff Pinner wrote:
> Just to sanity check I navigated to www.google.com -- the page load made 11
> requests, each with the same 8 identical cookies. Thus the reference set in
> this example saves 8 bytes per frame (as opposed to the 1.57 bytes in your
> analysis).
> 
> I'd suggest trying to capture data on a single domain to show the affect
> the compression has on repeated cookies.
> 

Here I was being pleased at how much like a real-world middleware
traffic that test was.

Good example results for what we middleware people have been saying
about the compression, TLS, etc. having very little benefit compared to
the amount of CPU/RAM resource consumption required to maintain the state.

PS. The HTTP/2 test data so far appears to have been very biased towards
traffic as seen on connections which are terminated at a origin server
or browser / UA client simply by being grouped by :authority. Traffic as
seen by middleware is much more volatile.

Amos
Received on Friday, 31 January 2014 17:24:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:24 UTC