Already done the 1rst thing: increased the pool size from JMeter. The results do not differ much, and this is my dilemma. You see, there are limits when increasing the pool size of requests, depending on the Tomcat configuration (no of active threads, request queue lenght , for example), and it was the first possible think to do when I noticed the server could do more.
I changed and studied the heap size and thread pool size in Tomcat, but nothing new happened. The problem is: I have only 196 out of 200% CPU occupied and I cannot see why. The "top" command shows me Cpu(s): 80.2%us, 11.7%sy, 0.0%ni, 5.9%id, 0.0%wa, 0.5%hi, 1.8%si, 0.0%s which means that some 5.9 of the processor is idle, while in Jmeter I have 100 threads running in a loop making requests, and in Tomcat I have 150 threads able to run simultaneously. Netstat -t shows me the receiver queue is empty, so everything is being handled, but still, a part of the processor is resting. Why ?! [Thank you for the responses] -- Kind regards / Freundliche Gruesse, Gabriela Gheorghe Email: [EMAIL PROTECTED] / [EMAIL PROTECTED] On 6/26/07, Michele Mazzucco <[EMAIL PROTECTED] > wrote:
On Tue, 2007-06-26 at 10:22 +0200, Gabriela Gheorghe wrote: > Thanks for the reply! > > The problem is not caused by I/O, because my web services do no > operations on the disk. The client is a JMeter instance and the CPU > load on the client machine is almost nothing (less than 8-10 %). > Try to increase the number of threads in JMeter. > So what I am looking for is for tuning some other parameters in > Tomcat, beside heap size and connection timeout. I am still loking for > the explaination. > Actually they do if services return results to JMeter. You could also try to increase the tomcat/axis2 thread pool size. Michele > All the best, > Gabriela > > On 6/25/07, Michele Mazzucco < [EMAIL PROTECTED]> wrote: > > On 25 Jun 2007, at 19:33, Gabriela Gheorghe wrote: > > > The problem is that I cannot run as many / time-consuming > requests > > so that > > the processor on the server reaches 100% CPU load. It only > reaches > > 90%, so > > the measurements for throughput that I need to obtain by > this testing, > > cannot be too relevant; I want 100% of the CPU working. > > > Are you sure that the bottleneck is not the client? > > > So my question would be - why is 10% of the CPU idle ? > > Couldn't it be because of I/O? > > > > Michele > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- > Kind regards / Freundliche Gruesse, > Gabriela Gheorghe > > Email: [EMAIL PROTECTED] / [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
