On 1 May 2014 16:19, <[email protected]> wrote: > Hi Sebb, > > It's probably because I am running tests within the same network, I > shouldn't hit caching as I am using different variables per request. I'd > expect at least 1 ms. > > No, I am not using HTTP Cache Manager? > > Can the timer resolution be made more granular?
Timer resolution is generally a function of the OS, also the hardware may be relevant. > Many Thanks > > Paul > > On Thu, 1 May 2014, at 08:00 AM, sebb wrote: >> On 1 May 2014 15:53, <[email protected]> wrote: >> > Hi, >> > >> > I am using an Aggregate Report listener. I have a minimum HTTP response >> > of 0 ms. But how can this be so? How can a web transaction be less than >> > 1 ms? >> >> Possible causes: >> - Fast webserver/network >> - The timer resolution may be insufficient to measure the response >> time accurately. >> - Are you using HTTP Cache Manager? >> >> > Many Thanks >> > >> > Paul >> > >> > >> > --------------------------------------------------------------------- >> > 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] >> > > --------------------------------------------------------------------- > 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]
