On Tue, Jun 12, 2001 at 07:48:57PM -0400, Matt Ellison wrote:
> There are a couple slightly different versions of this program. The current
> version has been tuned to cache everything it does in hashes per iteration
> through the handler sub - database queries, reading of HTML templates, etc.
> Suddenly (with no changes in the $r->print statements) I'm getting this
> enormous "failure" rate. I have seen the percentage of "Failed Requests" be
> as high as 75%, but we can't seem to figure out why.
>
> Something tells me that this isn't really a problem with our program. While
> I hammer it with ab, I get perfect pages every time (in every browser you
> can think of.) I read some discussion on archives of this list about using
> length() on a pre-built string to determine what should go into the
> Content-Length header, but this seems silly - especially if you need the
> page to interact with the browser dynamically (as in calling JavaScript
> functions on the fly as the output is being generated.)
http://www.mail-archive.com/modperl@apache.org/msg18544.html
Might be the answer to why your ab 'fails' some times.
> Can anyone shed some light on exactly what is happening with ab here? I
> have verified that there is no Content-Length header in the output via
> telnet to the Apache server, but how safe is it to omit this header? Why is
> the results with ab inconsistent?
The Content-Length header is necessary if you want keep-alive connections to
work.
--
Thomas Eibner <http://thomas.eibner.dk/> - DnsZone <http://dnszone.org/>
mod_pointer <http://stderr.net/mod_pointer>
