https://issues.apache.org/bugzilla/show_bug.cgi?id=48799
Pieter Ennes <apache....@spam.ennes.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
--- Comment #2 from Pieter Ennes <apache....@spam.ennes.nl> 2010-02-23 22:15:10
UTC ---
For us the aggregated value is of use in case of a redirect or when embedded
elements are loaded.
After a hardware upgrade on the server side, the relative 'processing' time is
likely to drop more rapidly than the measured download time, i.e. the
'transfer' time, if defined as t-pt would stay the same.
On the other hand, after a network upgrade, the total time is likely to drop
more than the processing time. Hence one could differentiate between a hardware
upgrade (t-pt the same), and a network upgrade (t-pt decreased).
Additionally, in case of a redirect, the aggregated processing time in the
parent element could give something like a user-experienced latency, since he
only starts seeing things after the last page.
Finally: since the size, connect and total times are already aggregated, my
symmetry neuron liked to see the same for the latency but without disturbing
anything, hence processing time.
What is your opinion?
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscr...@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-h...@jakarta.apache.org
