I'm getting a bottleneck on my JMeter clients when running distributed tests over 48 concurrent threads.
Scenario:
Hw: - 3 clients + 1 JMeter console (4 nodes total) - Each node: Pentium IV 2.4 GHz processor, 1 MB RAM
Sw: W2K SP4 JMeter 1.9.1 SUN JRE 1.4.2
JMeter 1.9.1 test: - Default JMetet.properties for all 3 clients. - Single thread group - 23 HTTP Request samplers (JSPs, GIFs, JSs, servlet calls) - 10 customized user logins (User Parameters) - "Retrieve all images and java applets" option unchecked. - "Functional test mode" option unchecked - No listeners enabled (just to rule them out) - Small throttle (constant timer of 100 ms for each sampler) - HTTPS protocol
Client CPU usage reaches 100% with only 48 concurrent threads, which is far too low for test requirements. Even with Graph results and Aggregate report listeners enabled, clients get saturated before JMeter console does.
I tried with different JRE implementations (IBM's 1.4.1, W2K's) with similar behaviour. My questions are:
1- Is this a normal behaviour for JMeter? I would expect JMeter console to saturate before clients do when listeners are enabled. Besides, 48 concurrent clients seems a bit low to me.
2- How could I increase concurrency without increasing the number of client nodes or raising throttle?
_________________________________________________________________
Reparaciones, servicios a domicilio, empresas, profesionales... Todo en la gu�a telef�nica de QDQ. http://qdq.msn.es/msn.cfm
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
