Hi Toni, Just some things I’ve noticed with JMeter/Java...
a) One JVM only supports 2000 concurrent TCP connections. Check your Time_wait states! b) Using HTTPS I've determined that about 70 threads per JVM is about the max you should do although I haven't investigated it into much detail. Seems to be pretty independent of processing power. I don't know the value for HTTP. Because of such issues I've written my own distributed test harness for JMeter. What I basically do is start separate instances of JMeter and let them execute at predetermined times. What I've noticed though is, that although one JVM/JMeter client can't go above 70 threads I can run multiple of these on one machine (P4HT 3Ghz). So far I've tried 3 concurrent. That to me shows that the treading used by Java is not as efficient as the Linux threading/multitasking. If you had this kind of set-up the question about distributing to multiple processors would be mute because you could do one JVM per processor (or even more than that if you like). That then finally maxes out the CPU! Ask my electrician! I flipped the circuits in our server room a couple of times with my harness going full blast. ;-) This set-up also gives you the ability to execute different scripts at the same time without having to have everything in one script. My 2ct. Hope it helps. Cheers Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
