On 25/06/07, Cristian Opincaru <[EMAIL PROTECTED]> wrote:
Hi all,
I'm trying to determine the throughput for some webservices implemented in
AXIS 1.4 which is running on top of Tomcat. The services are hosted on a
Linux Pentium 4 machine; I'm using another similar machine to run JMeter.
The puzzling thing is that I'm not able to bring the processor on my server
to 100%. It goes to about 90%, but not higher. Since the processor is 10%
idle, I assume that the throughput measurements are incorrect.
Why? There may be resource waits (e.g. socket closes) involved.
Also, do you really want to run your server at 90% CPU? I don't know
if you watched the Google talk about performance testing (link posted
to this mailing list recently), but the presenter said that one should
aim for at most 80% busy on Unix.
I'm trying to figure out why the cpu does not get to 100% usage. It's not
the network (the two are connected by a 100MB link). The simplest service is
a hello world, where no disk access is involved, therefore, I assume that
the throughput bottleneck should be the processor. But it's not 100% used.
What is the resource utilisation on the JMeter machine?
What are the other resource utilisations (memory, disk)?
If the JMeter system is running short of resources, you can reduce the
JMeter resource requirements by using non-GUI mode, using only one
listener, and reducing Assertions as far as possible.
Or you can add a second JMeter machine.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
