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. -- Robin D. Wilson Sr. Director of Web Development KingsIsle Entertainment, Inc. www.KingsIsle.com --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
