Anders Nielsen wrote: [...]
[...]I have been doing some testing with ab and I found some interesting cases.
On our production system I get the following when testing an important mod_perl enabled script from my local desktop:
$ ab -n 100 -c 5 "http://www.xxxxxx.dk/cgi/xxxxxx.cgi?q=test&allowall=1";
Failed requests: 21 (Connect: 0, Length: 21, Exceptions: 0)
Googling helps :) Rich Graves says:
http://my.brandeis.edu/bboard/q-and-a-fetch-msg?msg_id=0001GK
(Ignore "failed requests" -- ab considers it a failure when content is different, but that should be true for a dynamic page.
So if they were supposed to give the same content, than you have something to look at.
There are 21 failed requests which is surprising to me. The error type is Length. What does this mean? I don't see any explanation of the output of ab on the man page.
When testing our development server I sometimes get this error from ab: Completed 1000 requests Completed 2000 requests Completed 3000 requests apr_recv: Connection reset by peer (104) Total of 3320 requests completed
I don't know what this mean either. I am not sure why the ab would die of this kind of error instead of just reporting that an error happened.
Could be some problem in Apache or mod_perl. That normally means that the server has aborted the connection.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
