I've been benchmarking trafficserver using ab.
For a backend I'm using httpd with a module to insert
a delay into each request, as a crude simulation of
a heavyweight app likely to benefit from acceleration.

Results through trafficserver show most requests
reported as failing with "length", meaning the contents
aren't received in full (or at all).  A short ab run
with verbosity turned up shows lots of instances of:

LOG: header received:
HTTP/1.0 304 Not Modified^M
Date: Mon, 21 Nov 2011 14:23:48 GMT^M
Server: ATS/3.0.1^M
ETag: "5e24-24cd-4b23b69f6e89c"^M
Cache-Control: max-age=60^M
Age: 2^M
^M

WARNING: Response code not 2xx (304)


According to ab, this is in response to:
GET /testfile.html HTTP/1.0^M
Host: localhost^M
User-Agent: ApacheBench/2.3^M
Accept: */*^M
^M

i.e. an unconditional request!


This looks infeasibly broken.  Any clue what I'm missing?

-- 
Nick Kew

Reply via email to