jmeter - Confusion in choosing delay between Iterations -




my goal give exact 5000 milliseconds delay between iterations. below 2 approaches have followed.

approach #:1 :threadgroup>add testaction>add jsr223 timer (see below screenshot).

i clear on approach #1 , can see below lines in jmeter.log(5000-prev gettime)from got confirmation delay between iterations working.

2017-08-21 16:23:08,260 info o.a.j.t.jsr223timer: 4831

2017-08-21 16:42:37,871 info o.a.j.t.jsr223timer: 4835

approach #:2 : threadgroup>add testaction (see below screenshot).

after executed test in jmeter.log, couldn't find number indicating delay between iterations.

my questions: 1.for 5000 milliseconds delay between iterations approach should follow approach #:1 or approach # 2. 2.if use approach #:2 how can , can cross check 5000 milliseconds applying each iterations. 3.is approach #:2 correct mean missing anything?

please advise me! soo confused.

enter image description here

enter image description here

enter image description here

thanks, raj

  1. your approach #1 flaky

  2. your approach #2 fine.

where expect see evidences of delays? jmeter log won't contain lines indicating sleep happened , .jtl results file neither show test action sampler result(s) nor jsr223 timer (unless put sampler under transaction controller in "parent sample" mode configured store duration of pre/post processors , timers).

the way see "sleep" works running test 2 times: , without "sleeps" (better 1 virtual user), total duration of test "sleeps" enabled should 5 seconds longer.





wiki

Comments

Popular posts from this blog

Asterisk AGI Python Script to Dialplan does not work -

python - Read npy file directly from S3 StreamingBody -

kotlin - Out-projected type in generic interface prohibits the use of metod with generic parameter -