>>>>> "J" == Jon Stevens <[EMAIL PROTECTED]> writes:
>> /usr/sbin/ab -n 100 -c 10 http://maya:8080/gate/servlet/gate/
>> /usr/sbin/ab -c 10 http://maya:8080/gate/servlet/gate/
J> Both of these show a concurrency of 10. Is that what you really
J> meant to use?
yes, or at least, I believe so ;) In the field, my deployed app must
handle index page requests at a concurrency level of 40, with
turnaround times of only a few seconds.
I really don't know ab that well (at the source level) but I'd expect
it would sit on a thread's connection until it gets a response, only
what appears to be happening is that it gets disconnected and moves on
to the next, either due to this exception, or this is what is causing
it.
I've run this same test on plain tomcat jsp webapps without receiving
this stacktrace, but let me just sit on it a bit and see if I can get
more detail -- I mostly wanted to know if anyone else gets a
stacktrace when using rapid accesses through using ab. As I mentioned
before, the concurrency does not appear to bother the app, only when
more than one request comes down the same ab thread.
--
Gary Lawrence Murphy <[EMAIL PROTECTED]> TeleDynamics Communications Inc
Business Innovations Through Open Source Systems: http://www.teledyn.com
"Computers are useless. They can only give you answers."(Pablo Picasso)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
