Thanks for your quick reply. Does it mean that's just as expected ? Is there any better way to avoid this 'empty cache' effect in first time test run ?
I may run the first loop in a test group, e.g., 'first-time setup', with a larger expected time. Then, run the rest of the test instances in my 'normal' test plan with 200ms time. -- View this message in context: http://jmeter.512774.n5.nabble.com/long-latency-in-jmeter-first-time-test-run-tp5714748p5714894.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]
