--- Remedy QA <[EMAIL PROTECTED]> wrote:
> I have a few more questions/comments about how
> JMeter measures response times.
> Suppose I have the following Test Plan structure
> that is set to run twice by one user:
>
> Test Plan
> Thread Group
> HTTP Cookie Manager
> Simple Controller 1
> HTTP Request A (Retrieve all embedded
> resources)
> HTTP Request B (Retrieve all embedded
> resources)
> Timer - 5 seconds
> Aggregate Report 1
> Simple Controller 2
> HTTP Request C (Retrieve all embedded
> resources)
> HTTP Request D (Retrieve all embedded
> resources)
> HTTP Request B (Retrieve all embedded
> resources)
> Aggregate Report 2
>
> 1. There doesn't seem to be an option for JMeter to
> not retrieve embedded resources once it has been
> retrieved the first time. In other words for JMeter
> to simulate a browser cache. In my example, the
> first loop will retrieve all embedded resources for
> all the requests. The second loop through would do
> the same for the same user. Furthermore, it would
> be nice during the first loop, when encountering
> Request B again in Simple Controller 2, that it
> would not retrieve embedded resources for Request B.
> So it would seem that the response time for the
> requests will always be measuring "first cache hit"
> scenario.
>
I think Thad is working on implementing this. I have
no idea how far he has gotten. Currently JMeter does
not simulate brower cache this way. The way other
users handle this is to have a thread group that gets
all resources and other threads that do not.
> 2. Peter, you said that JMeter measures the total
> elapsed time. Just to clarify....For example, on a
> HTTP Request A that is run only once, does the
> measurement time start when the first byte request
> is sent and the measurement time stops when the very
> last byte response is returned which could well be
> the byte from an embedded file? Or is it the
> measurement starts after a virtual user has sent the
> last byte of the request and ends when the user
> retrieves the first byte of the response.
>
Basically the timer starts before the connection is
made and the end time is after the last resource is
read to bytes.
>
> 3. The Timer under the first HTTP Request B does
> not get calculated to the response time for
> Aggregate Report 1, which is what I want. However,
> if using the Transaction Controller, it does.
> Transaction Controller should have an option to
> measure with Timers or not.
>
right now only the transaction controller will
aggregate.
> 4. I suppose JMeter currently does not measure the
> number of KB a page request/response takes? Is this
> planned to be implemented?
you can always look at the server log to see how many
bytes were sent. getting the bytes should be that
hard. feel free to file an enhancement in bugzilla and
hopefully someone will get to it.
>
> Thanks,
> Mabel
>
>
peter
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
