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

Re: Negotiating compression

From: Willy Tarreau <w@1wt.eu>
Date: Thu, 29 May 2014 18:01:10 +0200
To: David Krauss <potswa@gmail.com>
Cc: Michael Sweet <msweet@apple.com>, Jason Greene <jason.greene@redhat.com>, Martin Thomson <martin.thomson@gmail.com>, Simone Bordet <simone.bordet@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20140529160110.GN25451@1wt.eu>
On Thu, May 29, 2014 at 11:12:07PM +0800, David Krauss wrote:
> On 2014?05?29, at 11:00 PM, Michael Sweet <msweet@apple.com> wrote:
> > I do appreciate your efforts.  But 100 instructions per byte is at least one order of magnitude more instructions than a literal copy of those bytes requires...  For 16k worth of header data that translates into 1.6 million instructions executed just for one header frame - fairly significant for an embedded processor?
> If the MCU sees more than a hundred Huffman-encoded bytes per stream, you?re Doing It Wrong.
> There are plenty of other ways for a malicious party to crash a printer. 1.6
> million instructions is still only a blink of an eye even for a small MCU.

Well, 1.6M instructions for a request is huge, whatever the processor size.
That would basically limit a 3 GHz CPU to 2000 requests/s when it can currently
do 300000 in http/1.1. I'm starting to be really worried...

Received on Thursday, 29 May 2014 16:02:05 UTC

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