unfortunately, XML is heavy weight and the default xml parser shipped with
sun jdk is crimson. it's rather slow, so the practical limit per system is
roughly 20-40 depending on the CPU speed. The only way to simulate larger
loads is to increase the think time, or use several client systems to
generate load.
on a 1.4Ghz Pentium M laptop, the limit for soap performance is around
20-25. If you check use memory cache in the webservice soap sampler, you get
up to 50, but at that point the test is measuring XML performance on the
server. hope that helps
peter
On 12/2/05, Ross Garrett <ross.garrett@mobilecohesion.com> wrote:
>
> Hi
>
> I have just started using JMeter for performance testing of web service
> applications. I am currently using one thread group, and have been
> trying various numbers of threads. The maximum performance I can get
> (using 30-35 threads) is approx. 140tps which I know is just over half
> the current benchmark for the service under test.
>
> Should I be configuring JMeter differently to achieve higher
> performance, or will it just not go any faster?
>
> Thanks in advance
>
> /Ross
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
|