Can you provide your test plan or give more details about the options you use in your sampler:
- So you said HC 3.1 (regarding HC4 the cookie issue you report is fixed) - Do you use embedded resources download ? - Do you use concurrent download option ? size of pool ? - keepalive ? Regards Philippe On Tue, Nov 15, 2011 at 6:37 PM, sebb <[email protected]> wrote: > On 15 November 2011 17:24, Robin D. Wilson <[email protected]> wrote: > > Hopefully this list can handle images... > > No, it cannot. > > Use a public hosting service and include the URL in the e-mail. > > > I have included a couple screen snaps of what I'm seeing. I ran a test > that > > requests (GET) the 'homepage' from our test machine. Then it POSTs a > login > > (username + password + special token) to the login form. It is a very > > simplified test. > > > > When I run it on JMeter 2.4, I get throughput of 128.1. When I run it on > > JMeter 2.5.1 I get throughput of 79.5. > > > > The request averages show similar differences: > > > > JMeter 2.4 - average times are 744ms > > JMeter 2.5.1 - average times are 901ms > > > > Re-running the tests over and over give very similar results (there's > some > > variability in the response times of the server, so I had to run this a > > bunch of times to be sure that I wasn't just seeing an anomaly. The > results > > are consistent - each test run shows JMeter 2.4 running significantly > faster > > than JMeter 2.5.1. > > Do you use HTTP or HTTPS? > > Do both GET and POST show elapsed time increases? > > > BTW, just now, when I tried to switch this test to use the HTTP4 client, > the > > cookies stopped working correctly. So I couldn't test that sampler. The > > above numbers are just for the HTTP3.1 client. I have a cookie value > called > > 'stk', and using the "${COOKIE_stk}" variable in the POST fails about > 90% of > > the time when I'm using the HTTP4 client. It works fine with HTTP3.1. > > There have been some fixes to HC4 since 2.5.1. > > > -- > > Robin D. Wilson > > Sr. Director of Web Development > > KingsIsle Entertainment, Inc. > > VOICE: 512-777-1861 > > www.KingsIsle.com > > > > > > -----Original Message----- > > From: sebb [mailto:[email protected]] > > Sent: Tuesday, November 15, 2011 10:09 AM > > To: JMeter Users List > > Subject: Re: JMeter reporting higher response times > > > > On 15 November 2011 15:58, Robin D. Wilson <[email protected]> wrote: > >> Not sure if this will matter, but have you tried testing this in > >> JMeter 2.4.x? > >> > >> The reason I ask is that I have a bunch of test scripts that I > >> regularly run in 2.4 r961953, and I have seen a significant decrease > >> in performance of these same test scripts (both unmodified, and > >> switching to various flavors of the new HTTP Sampler) when I switched to > > 2.5 and 2.5.1. > > > > Can you provide details of these issues please? > > > >> -- > >> Robin D. Wilson > >> Sr. Director of Web Development > >> KingsIsle Entertainment, Inc. > >> VOICE: 512-777-1861 > >> www.KingsIsle.com > >> > >> > >> -----Original Message----- > >> From: sasidharsmit [mailto:[email protected]] > >> Sent: Tuesday, November 15, 2011 9:08 AM > >> To: [email protected] > >> Subject: Re: JMeter reporting higher response times > >> > >> I disabled everything other than the actual sampler. Still, the > >> response time is over 2000 ms. PF attached the screenshot. > >> > >> http://jmeter.512774.n5.nabble.com/file/n4994555/jmeter_only_sampler.p > >> ng > >> jmeter_only_sampler.png > >> > >> Regards, > >> Sasidhar Sekar > >> > >> -- > >> View this message in context: > >> http://jmeter.512774.n5.nabble.com/JMeter-reporting-higher-response-ti > >> mes-tp > >> 4994460p4994555.html > >> Sent from the JMeter - User mailing list archive at Nabble.com. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [email protected] > >> For additional commands, e-mail: [email protected] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cordialement. Philippe Mouawad.
