RE: Choosing a header compression algorithm
RUELLAN Herve <Herve.Ruellan@crf.canon.fr> Mon, 25 March 2013 17:23 UTC
Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0871521F9512 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 25 Mar 2013 10:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level:
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KwpPYAmGB2tS for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 25 Mar 2013 10:23:30 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF5F21F94F3 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 25 Mar 2013 10:23:29 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UKB67-000377-Cm for ietf-http-wg-dist@listhub.w3.org; Mon, 25 Mar 2013 17:22:15 +0000
Resent-Date: Mon, 25 Mar 2013 17:22:15 +0000
Resent-Message-Id: <E1UKB67-000377-Cm@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <Herve.Ruellan@crf.canon.fr>) id 1UKB5v-00034u-JN for ietf-http-wg@listhub.w3.org; Mon, 25 Mar 2013 17:22:03 +0000
Received: from inari-msr.crf.canon.fr ([194.2.158.67]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <Herve.Ruellan@crf.canon.fr>) id 1UKB5t-0006aN-Nx for ietf-http-wg@w3.org; Mon, 25 Mar 2013 17:22:03 +0000
Received: from mir-bsr.corp.crf.canon.fr (mir-bsr.corp.crf.canon.fr [172.19.77.99]) by inari-msr.crf.canon.fr (8.13.8/8.13.8) with ESMTP id r2PHLVSK004485; Mon, 25 Mar 2013 18:21:31 +0100
Received: from ADELE.crf.canon.fr (adele.fesl2.crf.canon.fr [172.19.70.17]) by mir-bsr.corp.crf.canon.fr (8.13.8/8.13.8) with ESMTP id r2PHLVlF007753; Mon, 25 Mar 2013 18:21:31 +0100
Received: from ADELE.crf.canon.fr ([::1]) by ADELE.crf.canon.fr ([::1]) with mapi id 14.02.0342.003; Mon, 25 Mar 2013 18:21:31 +0100
From: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
To: Mark Nottingham <mnot@mnot.net>
CC: Roberto Peon <grmocg@gmail.com>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Thread-Topic: Choosing a header compression algorithm
Thread-Index: AQHOJgaI2I9gxWQLAUOB6sMRXNhzJpixMSEAgAB5jdCAAEKngIAAFPgQgAPbnwCAAMyn8A==
Date: Mon, 25 Mar 2013 17:21:30 +0000
Message-ID: <6C71876BDCCD01488E70A2399529D5E5163F4076@ADELE.crf.canon.fr>
References: <254AABEE-22B9-418E-81B0-2729902C4413@mnot.net> <A14105FB-ED1A-4B70-8840-9648847BCC3A@mnot.net> <6C71876BDCCD01488E70A2399529D5E5163F3C67@ADELE.crf.canon.fr> <CAP+FsNfFohSwrX2DxthNcnn+wDj6T5W7xpcg4yA56Gvt_nP3_Q@mail.gmail.com> <6C71876BDCCD01488E70A2399529D5E5163F3D72@ADELE.crf.canon.fr> <7CA7F3EB-A492-471A-8AC4-23293DD10840@mnot.net>
In-Reply-To: <7CA7F3EB-A492-471A-8AC4-23293DD10840@mnot.net>
Accept-Language: en-US, fr-FR
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.20.8.8]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Received-SPF: none client-ip=194.2.158.67; envelope-from=Herve.Ruellan@crf.canon.fr; helo=inari-msr.crf.canon.fr
X-W3C-Hub-Spam-Status: No, score=-5.0
X-W3C-Hub-Spam-Report: AWL=-1.823, BAYES_00=-1.9, RP_MATCHES_RCVD=-1.302
X-W3C-Scan-Sig: maggie.w3.org 1UKB5t-0006aN-Nx d77a7a3370838cd153808ae307b336a1
X-Original-To: ietf-http-wg@w3.org
Subject: RE: Choosing a header compression algorithm
Archived-At: <http://www.w3.org/mid/6C71876BDCCD01488E70A2399529D5E5163F4076@ADELE.crf.canon.fr>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17133
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
> -----Original Message----- > From: Mark Nottingham [mailto:mnot@mnot.net] > Sent: lundi 25 mars 2013 06:56 > To: RUELLAN Herve > Cc: Roberto Peon; ietf-http-wg@w3.org Group > Subject: Re: Choosing a header compression algorithm > > > On 23/03/2013, at 5:04 AM, RUELLAN Herve <Herve.Ruellan@crf.canon.fr> > wrote: > > > I think it would be good to move this from the compressors to the > streamifier. In addition, it would be interesting to look at a more realistic > streamifier that could for example unshard hosts (expecting that HTTP/2.0 > will remove the sharding currently done by server developers). > > Right now, it combines all requests to the same TLD (according to the Public > Suffix List) into a single "connection." Do you have a suggestion for how to do > it better? I think this should provide some "realistic" results as a starting point. Depending on what we want to measure, we may want to refine this a bit. Hervé. > I've just pushed a quick and dirty fix to use a new instance of each > compressor for each connection; the results are pretty even between > headerdiff and delta2, with a small increase in each: > > * TOTAL: 5948 req messages > size time | ratio min max std > http1 3,460,925 0.18 | 1.00 1.00 1.00 0.00 > delta2 (max_byte_size=4096) 707,901 11.87 | 0.20 0.03 0.83 0.15 > headerdiff (buffer=4096) 960,106 1.65 | 0.28 0.01 0.96 0.23 > > * TOTAL: 5948 res messages > size time | ratio min max std > http1 2,186,162 0.28 | 1.00 1.00 1.00 0.00 > delta2 (max_byte_size=4096) 622,837 12.86 | 0.28 0.02 1.22 0.13 > headerdiff (buffer=4096) 596,290 3.65 | 0.27 0.02 0.92 0.18 > > Cheers, > > > -- > Mark Nottingham http://www.mnot.net/ > >
- Re: Choosing a header compression algorithm Stephen Farrell
- Choosing a header compression algorithm Mark Nottingham
- RE: Choosing a header compression algorithm RUELLAN Herve
- Re: Choosing a header compression algorithm James M Snell
- Re: Choosing a header compression algorithm Roberto Peon
- Re: Choosing a header compression algorithm Mark Nottingham
- Re: Choosing a header compression algorithm Roberto Peon
- RE: Choosing a header compression algorithm RUELLAN Herve
- Re: Choosing a header compression algorithm Roberto Peon
- RE: Choosing a header compression algorithm RUELLAN Herve
- Re: Choosing a header compression algorithm Martin Thomson
- Re: Choosing a header compression algorithm Roberto Peon
- Re: Choosing a header compression algorithm Mark Nottingham
- Re: Choosing a header compression algorithm Mark Nottingham
- RE: Choosing a header compression algorithm RUELLAN Herve
- Re: Choosing a header compression algorithm Roberto Peon
- Re: Choosing a header compression algorithm Roberto Peon
- RE: Choosing a header compression algorithm RUELLAN Herve
- Re: Choosing a header compression algorithm Roberto Peon
- Re: Choosing a header compression algorithm Roberto Peon
- Re: Choosing a header compression algorithm Roberto Peon
- Re: Choosing a header compression algorithm James M Snell
- Re: Choosing a header compression algorithm Roberto Peon
- RE: Choosing a header compression algorithm RUELLAN Herve
- RE: Choosing a header compression algorithm RUELLAN Herve
- Re: Choosing a header compression algorithm Roberto Peon
- Re: Choosing a header compression algorithm Roberto Peon
- RE: Choosing a header compression algorithm RUELLAN Herve
- Re: Choosing a header compression algorithm Roberto Peon
- Re: Choosing a header compression algorithm James M Snell