On 29/05/2008, Pieter Ennes <[EMAIL PROTECTED]> wrote:
> sebb wrote:
> > On 29/05/2008, Pieter Ennes <[EMAIL PROTECTED]> wrote:
> >> Hi all,
> >>
> >> I was wondering why the latency time ('lt') for nested HTTP requests is
> >> not propagated to its parent sample, while the normal time ('t') is.
> >>
> >> <httpSample t="1645" lt="0" ts="1212063826434" s="false" lb="HTTP
> >> Request" rc="200" rm="OK" tn="Thread Group 1-1" dt="text" by="92031">
> >> <httpSample t="428" lt="427" ts="1212063826434" s="true"
> >> lb="http://cnn.com/"; rc="302" rm="Found" tn="Thread Group 1-1" dt="text"
> >> by="260"/>
> >> <httpSample t="1217" lt="399" ts="1212063826862" s="true"
> >> lb="http://www.cnn.com/"; rc="200" rm="OK" tn="Thread Group 1-1"
> >> dt="text" by="91511"/>
> >> </httpSample>
> >>
> >> In the above snippet, the outer t=1217+428=1645, but the outer lt=0. Is
> >> there a reason for this?
> >>
> >
> > Probably because it was overlooked...
> >
> > I assume the latency should be saved from the first child, as that was
> > the first response?
>
>
> I'd say it should be the sum of the two childs, as the behaviour of 'lt'
> then matches 't'.
>
Latency = time to first response.
I don't think it makes sense to add latencies - likewise one does not
add minima or maxima.
> Ciao,
>
> --
>
> - Pieter
>
> ---------------------------------------------------------------------
> 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]
