Hi, This doesn't sound right, are you sure? Response time is calculated from the moment the request was sent to the moment when the last bit of the response was received. So it can't include wait times. If your sampler would do some processing (for example the beanshel sampler), the response time might include processing time and it is obvious when the test machine is overloaded.
Are you noticing the problem only when using transaction controller? (I have to admit, this sounds like a problem of the application-under-test, its usually is in circumstances like this) On Wed, Jun 22, 2011 at 8:54 AM, Andrej van der Zee < andrejvander...@gmail.com> wrote: > Hi, > > I have a question about the Constant Throughput Timer. I have the > following configuration: > > Thread Group (10 threads) > ---> Transaction Controller > -------> HTTP Request > ---> View Results In Table > ---> Constant Throughput Timer (60 samples per minute) > > Now I noticed that the waiting time for the threads is included in the > elapsed sample time. So with 10 threads and 60 samples per minute, the > elapsed time will go to the 20 seconds (provided the threads are > scheduled round-robin, which they are). But, I would like to count > only the elapsed time for the Transaction Controller, without the > waiting times caused by the Constant Throughput Timer. How can I make > this happen? > > Thank you, > Andrej > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
