Hello, I tried to reproduce your issue with the info you provided but I am not able to. It would be useful to submit a simplified test plan that reproduces the issue so we can see where it comes from.
Thanks Regards Philippe On Wed, Feb 29, 2012 at 4:40 PM, ivan.rancati <[email protected]>wrote: > Hello, > to summarize: > > - I did not tweak https.use.cached.ssl.context. Neither in the nightly, nor > in the released build. No changes to jmeter.properties, or > system.properties, I left the files untouched, as they were in the > downloaded .zip file. > > - In my test plan, I had some https calls. I disabled all of them long ago, > but I left the authorization manager, as I thought it would not be used > anyway. > With the nightly build: test plan runs fast, 240 req/second. With the 2.6 > release build, same test plan: 15 req/second. > > - Now I disabled the (unused) authorization manager. Test plan runs fast > with both 2.6 release and nightly build. > > regards, > Ivan > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Performance-difference-between-released-2-6-and-nighly-r1095243-tp5522066p5525278.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] > > -- Cordialement. Philippe Mouawad.
