Hi assuming you are referring to the response time of each sampler (and not throughput) - I do not see the behavior you are seeing Jmeter does not include the delay in the sampler times . However Throughput for e.g. in say Summary Report would include the delay in its calculation- so youll need to specify what and how you are measuring the time
On Wed, Sep 9, 2015 at 11:21 AM, Onl <[email protected]> wrote: > Hi, > > Should jmeter include timer delays in the results? > My tests has a Uniform Random Timer at the thread-level, such that: > > THREAD_ONE > UNIFORM RANDOM TIMER (max 100ms) > HTTP SAMPLE 1 > HTTP SAMPLE 2 > HTTP SAMPLE 3 > HTTP SAMPLE 4 > HTTP SAMPLE 5 > HTTP SAMPLE 6 > HTTP SAMPLE 7 > HTTP SAMPLE 8 > HTTP SAMPLE 9 ... > (hundreds of samplers) > > Thread count is 100, rampup is 100. > > > WITHOUT TIMER DELAY > ==================== > > 3.696, 1.709, 2.447 (recycle tomcat) > 3.801, 1.670, 2.488 (recycle tomcat) > > WITH TIMER DELAY > ================ > 3.678, 2.945, 5.305 (recycle tomcat) > 3.425, 2.974, 5.709 > > (time is in seconds) > > It was my understanding that timers are not included in the results. But > consistently, > my tests with the timers are nearly double the time than those without > after the first run. > > What is going on here? > Why is the time for the 2nd and 3rd iteration double? > Is there a way to exclude timer delays from the results? > Is there a flaw in my process? > > Thanks > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
