G'day You could now try different configurations to get increased throughput. Generally you should do better with more threads but only up to a limit of the number of threads the box can handle. With the power you have you can expect to use a lot more threads than 1 or 2 or 3.
If you are getting 2600 q/s with three threads then you are getting 860 q/s per thread. This is 1.16 ms per query per thread. If you went for six threads then at 2600 q/s you would be doing one query every 2.3 ms per thread. So to keep the load the same you would add a sleep of 1.14 ms. (Since you can't add such a sleep in JMeter you would add a 2 ms sleep but only execute the sleep on 57% of samples. Or you can do the sleep in the sampler, where you can sleep for 1.14ms, and ideally make the sleep time a sampler parameter.) If this run is good then cut the sleep in half and see if the run remains good. If it does you should get throughput of about 3468 q/s. Keep going till something breaks or you can't get extra throughput. (But I have to say I don't think you are going to get to the same throughput as with the C program. Where the response time of the system under test is so short you are really testing the load generation tool rather than the system under test. In this case you are comparing a flexible, general purpose tool against something custom built for one purpose. But who knows, you might the same throughput.) Ian Blavins Contract Performance Engineer Temenos -----Original Message----- From: Stefano Gambetta [mailto:[EMAIL PROTECTED] Sent: 23 May 2007 10:36 To: JMeter Users List Subject: Re: JMeter performance testing - heavy CPU utilization Hello, here are some news... Yesterday I repeated the tests using only the java request sampler in the scenario, without variables, without sleep time (next thing to try) and without listeners. This way CPU efficiency is better: after sometime after the beginning of the test, CPU starts to drop to about 90-80-70%. So I was able to raise the thread parallelism, up to 2-3 with some effects on the throughput. With that configuration, I have reached about 2600 q/s. This email (and any attachments) contains confidential information, and is intended only for the named recipient. Distribution or copying of this email by anyone other than the named recipient is prohibited. If you are not the named or intended recipient, please notify TEMENOS or the sender immediately and permanently destroy this email (and any attachments) and all copies of it. No member of TEMENOS Group AG or any of its associated or affiliated companies is liable for any errors or omissions in the content or transmission of this email. Any opinions contained in this email are solely those of the author and, unless clearly indicated otherwise in writing, are not endorsed by any member of TEMENOS Group AG or any of its associated and affiliated companies. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
