On Mon, 29 Oct 2001, Joshua Chamas wrote:
> > Complete requests: 1000
> > Failed requests:22
> >(Connect: 0, Length: 22, Exceptions: 0)
>
> If ApacheBench complains about length problems, it means
> that the length of subsequent requests differs from the
> output length of the fi
Philip Mak wrote:
>
> Time taken for tests: 21.109 seconds
> Complete requests: 1000
> Failed requests:22
>(Connect: 0, Length: 22, Exceptions: 0)
> Total transferred: 196578 bytes
> HTML transferred: 12714 bytes
> Requests per second:47.37
> Transfer rate:
Hello,
PM>I'm using ApacheBench to perform stress testing on my mod_perl server.
PM>It's not always working, though. Observe the following two runs: (first
PM>is Broken pipe; second has some failed requests)
Try writing a Perl (or other language) client that hits the URL you test
over and over a
Philip Mak wrote:
> I'm using ApacheBench to perform stress testing on my mod_perl server.
> It's not always working, though. Observe the following two runs: (first is
> Broken pipe; second has some failed requests)
>
> [pmak@sg1 bin]$ ./ab -n 1000 -c 10 http://65.119.108.120:8080/
> This is Apa
I'm using ApacheBench to perform stress testing on my mod_perl server.
It's not always working, though. Observe the following two runs: (first is
Broken pipe; second has some failed requests)
[pmak@sg1 bin]$ ./ab -n 1000 -c 10 http://65.119.108.120:8080/
This is ApacheBench, Version 1.3c <$Revisi
