a. I believe your site has a problem so I wouldnt see the point of having accurate response times , they would become invalid as soon as you tweaked your server so any ballpark estimate would do b. From firebug try out the home page when your server is loaded under different loads. Estimate the proportions between the cumulative time and observed times for static files e.g. if you have 60 resources and if you sequentially added up the times it takes 4 seconds , but firebug shows that the browser loads all 60 resources in 1 seconds. Repeat this with a browser and with cache cleared but with your server under a different load. You should be able to come up with a range that given a cumulative time for static resources you can estimate the time it would have taken for the browser(sum of default.aspx + time for static + time for render). Then use JMeter to figure out the cumulative time for the static resources on your page (simple addition) and use the proportion range you've calculated above to get the browser time. You can do this for if its a returning user (where the cache might be hit , but the browser may still make requests and get a 304 or something)
regards deepak On Thu, Sep 16, 2010 at 3:00 PM, Prostak <[email protected]> wrote: > > Thanks Deepak. Now I understand why you add in your case. However, my web > application is located on two servers with a load balancer. All resources > are identically stored on these two servers. No CDN or other servers are > involved (besides SQL servers, but homepage doesn't touch them). > How do I measure (or estimate) the response time for Home Page in my case? > -- > View this message in context: > http://jmeter.512774.n5.nabble.com/Test-plan-for-970-page-requests-every-5-min-tp2826174p2843057.html > Sent from the JMeter - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
