>Ok, let's assume I've done it and added this data in a fifth column. Would >the calculation be somewhat correct? If its matching yes - again I haven't seen your calculations . However I think your server is queueing requests , so you are going to get wildly varying times making it almost impossible to have any degree of certainty. Your first step should be to see what can be done about your server.
>What about the other one? "Non HTTP response message: Connection reset" - You need to check jmeter.log for your entire stack trace to see if theres any more information , but your socket was closed . >No, I am testing it against live server. What's the difference though? Dev servers usually dont have the hardware or the resources or the tuning to handle 150 concurrent threads. On Fri, Sep 17, 2010 at 11:06 AM, Prostak <[email protected]> wrote: > > >not enough to go through - An easy way to verify is when you have > generated > >load , access your site using a different machine and see the amount of > time > >the page takes on clean browser , it should be close to average time > > Ok, let's assume I've done it and added this data in a fifth column. Would > the calculation be somewhat correct? > > >Your client(Jmeter) tried to connect but timed out. > >Indicates server is under load and cant accept all the connections to it. > > What about the other one? "Non HTTP response message: Connection reset" - > when does this occur? > > >Again are you testing it against a dev system? > > No, I am testing it against live server. What's the difference though? > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Test-plan-for-970-page-requests-every-5-min-tp2826174p2844102.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] > >
