Config items and pre-processors are completed before the sample
starts, so are not included in timings.

However, if you use a Transaction Controller (rather than a Sampler),
this will include the time taken to run all of its children, including
timers, etc.

S.
On 19/07/06, Peter Lin <[EMAIL PROTECTED]> wrote:
the response time is the first byte sent to the last byte recieved.

peter


On 7/19/06, Willingham Geoff <[EMAIL PROTECTED]> wrote:
>
> From what little I have seen in the code, the response times will NOT
> include pre-processors etc.
>
> The calls to start/stop time logging are part of the sampler.  Thus,
> timings should include the time it takes for the sampler to send the
> request, the time spent waiting for a response, and the time taken to
> download the reply.
>
> The times should not include: the time taken to run the preprocessors,
> or the time taken to run any post processors (including assertions,
> regex, etc).
>
> Regarding config elements - I don't know whether they are done
> statically (before the script starts), as a preprocessor, or as part of
> the sampler.  Thus, I don't know whether they will affect the timings.
>
> Geoff
>
> -----Original Message-----
> From: prakash abraham [mailto:[EMAIL PROTECTED]
> Sent: 19 July 2006 15:44
> To: JMeter Users List
> Subject: Jmeter response time
>
> Hi experts,
>
> Im using a beanshell preprocessor for some calculation.
> My query is Do the response time logged by Jmeter includes the
> preprocessor execution time also ??
> Im also wondering how Jmeter record the response time, wether Jmeter
> records time at the start of getting the first byte or  wait to get the
> complete data..
>
> Thanks in Advance,
> Prakash Abraham
>
> This e-mail is confidential and privileged. If you are not the intended
> recipient please accept our apologies; please do not disclose, copy or
> distribute information in this e-mail or take any action in reliance on its
> contents: to do so is strictly prohibited and may be unlawful. Please inform
> us that this message has gone astray before deleting it. Thank you for your
> co-operation.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to