Sebb asked: >How do the average elapsed times compare?
The average times are about 50% longer than with 2.4 - so where I was averaging ~1000ms for the 'submit' (POST) action, it is now showing about 1500 to 1750ms. (I am mostly concerned with the 'POST' because that's where all the real work occurs on our server side.) >Also what about min/max std.dev? Those varied a lot from one run to the next anyway - just because I've always been dealing with very short durations - but I did notice that the 'max' seemed to consistently read higher than my prior benchmarks - but only by 1-2 seconds (1000-2000ms). Given the variables in the system - that doesn't seem too outrageous to me. >The http sampler code was re-organised for 2.5; additional classes were added and there is another code layer, >but I'd be surprised if that had a significant effect. I wonder if that mattered - it sure appears to be making a big difference. I think I could re-work the script to use AJP (we're hitting 'tomcat' through an apache front-end right now - and our apache uses AJP), but I have no prior benchmarks to compare AJP with... -- Robin D. Wilson Sr. Director of Web Development KingsIsle Entertainment, Inc. www.KingsIsle.com On 30 August 2011 20:19, Robin D. Wilson <rwils...@gmail.com> wrote: > I have a JMeter script that performs registrations on our website. On > JMeter 2.4, I am able to run this script with a throughput of ~160 > requests per second. With no other differences in the script, I run it > on JMeter 2.5 and only get about 78 requests per second (peak). > > I checked and modified configs for all the new "HTTP/4" vs "HTTP/3.1" > vs "Java" for the HTTP Request HTTP Client sampler, none of that made > any difference. > > Is JMeter 2.5 known for being slower? Or is there something I should > be examining in my configuration to get it to speed up? > The script consists of a 'master' script that includes a 'Registration' > sampler script. The 'master' script just allows me to setup the test > environment for my run, and having the 'registration' part included > lets me use that registration script in many different test plans. > > The registration script performs the following actions: > > HTTP Request HTTP Client - GET the homepage HTTP Request HTTP Client > - GET the registration form page HTTP Request HTTP Client - GET the > an AJAX request for our 'username suggestor' > HTTP Request HTTP Client - POST registration form HTTP Request HTTP > Client > - GET the homepage (as logged in user - based on JSESSIONID cookie) > > I generally run it with 100 threads, and have had very consistent > results when running it under JMeter 2.4. So this is really more of a > question about JMeter 2.5, and whether it added 50% more overhead to > the system somewhere, or if I am likely to have a configuration > problem that is throwing in extra delays. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
