I've just done a test using the Java Request / Java Test sampler in JMeter 2.2.
If I set the sleep_time and sleep_mask to 0, I can get a throughput of 20,000-30,000 per second. Obviously this uses around 100% CPU. For sleep_time of 10, I get an average elapsed of 15ms, and throughput of 64/sec which equates to 15.625ms per sample. The average figure of 15ms is rounded down, so this agrees with there being very little overhead. CPU usage is minimal. Note that I was using only the Summary Report listener. If the output is written to a file, then the throughput for the 0 sleep drops to 3,500-7,000/sec. However the rate for the 10ms sleep samplers is only marginally affected, e.g. 63.9 for CVS and 63.8 for XML with 1000 samples. The above suggests that JMeter is behaving well for the limited tests I performed. S On 22/05/07, sebb <[EMAIL PROTECTED]> wrote:
There could perhaps be a problem... What throughput did you get? What was the average sampler response time? Are you using any functions or variables? Which version of Java, and which OS? S. On 22/05/07, Stefano Gambetta <[EMAIL PROTECTED]> wrote: > Hello, > I'm evaluating JMeter as a load testing framework for my performance > analysis. > > I'm going to load test a DNS server. To do so, I've written my own Java > Request sampler, which issues DNS requests using the package dnsjava. > > My test configuration is very simple: one thread-group (one therad > configured for example), one java request sampler, one simple data writer as > listener. > > The problem basically is that with that configuration JMeter can reach a > very low throughput (query sent / sec), since during tests CPU get > saturated. > > The known bind queryperf tool can generate a load about six times higher > while using less than 30 % CPU. Since this tool is a simple C program, I > expected a greater performance, but that results seems to be exaggerated. > > I assumed that my sampler class was not well optimized, so I did a quick > profiling of JMeter, during the test, in order to discover some areas of > improvement. > > I think I saw an interesting result: most of the thread sampler time is > spent in one method of one particular class of JMeter, and a minor part is > spent inside the Java Request sampler. The mentioned method is: > > SamplePackage.setRunningVersion() > > > Giving that results, I have some questions: > > - what does that method do? > - is it possible to reduce its overhead? > > Thanks for any replies >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
