-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
Jean-Luc Rochat wrote:
> > and run ab -n 1500 -c 500 http://xxx/yyy/CountHit
> I don't rember ab was able to do > ~120 concurrent threads (fd/ process
> limit ?).
> and Apache (except if hacked(one variable, little hack) & recompiled) is
> limited to 254 sub-process. So you'll maybe have a queue.
Yes, I set this parameter to load mod_jserv but for my "true" servlet
I just use -c 30
> > I've two computers :
> > one bi P3 450 and one P3 450 (running apache)
> > during the test with ab, I get one JServ busy
> > if I try a new test, the JServ which was busy doesn't respond
> > It seems to be done forever ...
> I think that you maybe exceeded the processes capacity. Does the gc get
> spare time to start ?
> What's you heap size ? the answer is maybe here, do you knnow (option
> -verbosegc) if the gc starts ?
I'll make a test.
> What do you find in logs ?
Nothing interesting ;-)
> If you can't find annything, what about testing it whith another jvm ?
> the blackdown 1.1.7 is maybe less buggy, or IBM's ...
> or try Solaris. ;-) Lots of people think it's the most stable, and so do
> I.
Ok.
I've made a test with the same hardware and Solaris 2.7 (x86) last
jdk.
But Solaris was slow compare to Linux with high load.
Thanks.
Ludo
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
