- From: Jason Greene <jason.greene@redhat.com>
- Date: Thu, 29 May 2014 11:58:52 -0500
- To: Martin Thomson <martin.thomson@gmail.com>
- Cc: Willy Tarreau <w@1wt.eu>, David Krauss <potswa@gmail.com>, Michael Sweet <msweet@apple.com>, Simone Bordet <simone.bordet@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
On May 29, 2014, at 11:12 AM, Martin Thomson <martin.thomson@gmail.com> wrote: > On 29 May 2014 09:01, Willy Tarreau <w@1wt.eu> wrote: >> 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... > > That assumes that you need to decode header fields. There's no reason > you can't do a byte-by-byte comparison in many cases. That’s true. An optimal reverse proxy, for example, could do method/location/path matching using bitmasks, and pass the message as a direct copy. -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat
Received on Thursday, 29 May 2014 16:59:51 UTC