| || |
User (email@example.com) posted:
The web_concurrent_* block is usually used to wrap the request
for the resources on the page (frames, images, JS, css), which
uses the multiple connections that've been set up (the # of
concurrent connections setting).
If you want to check the time it takes for the 'whole' page
(including all resources to load), then this is correct.
If you want to time just the server response for the initial
page (without the resources), then you can put an inner
transaction for just the submit/url request.
Of course this assumes you're using the old HTTP method, and
not the new URL method (which unfortunately automagically
retrieves 'most' of the resources automatically).
--- In LoadRunner@y..., r_a_j_66@h... wrote:
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/