JMeter does not currently support concurrent downloads in a single thread, but this would affect all downloads of the same page. If any specifc samples are much longer then the most likely culprit is the server or network.
The Cache Manager may be used to simulate browser caching, which might be another factorm which explains the difference in timings. Wireshark can show what requests the browser makes; these can be compared with JMeter. On 30 March 2011 13:26, apc <a...@apc.kg> wrote: > No, JMeter is pretty fair with response times. > The problem is somewhere else. > > I suggest you put the load without AutoStop and look at online response > times. When they hit 20s - do request with your browser. I think you'll get > long waiting time. Because somewhere in your test infrastructure you get > high network delay. And this is not because of JMeter. > > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/question-about-duration-assertion-tp4269021p4271366.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org
