On 08/23/10 10:30, ankitR wrote: > > Hi, > > Thanks for the help. However I have some doubts. The manual time that I am > taking is when the server is loaded with the 50 users spawned by Jmeter. So > shouldn't the manual time also include the the time taken by all the > background scripts running on the webserver? > Secondly, I tried using firebug earlier and from what I understand it gives > you the load time of all the dom content, js. images ets loaded with the > page. I have enabled the download all embedded resources checkbox in my http > requests so Jmeter also gives me that time. I am not clear as to how firebug > will help me. would you please elaborate a bit. I am pretty new to jmeter > and other test tools. Please excuse my limited knowledge. > Thirdly, the manual time is taken when the server is loaded with infact 51 > users (50 jmeter + 1 manual). For just 1 jmeter user it shows 448ms as > opposed to 35s when there are 50 users. What I want is what the end user > sees when the server is having a load of 50 users, so I don't feel comparing > with 1 jmeter user will help. could you elaborate a bit upon what you meant? > If it helps I noted the time when there is only 1 manual user( Jmeter test > is not started) and it is 6.5s
I believe that was a misunderstanding on Deepak's part. The time you perceive during the Jmeter run is in fact what you want to compare to Jmeter's measured time. Use Firebug to find out how the total load times (including each last embedded element) relates to the time you perceive as the actual load time, i.e. how long it takes until you see the page. There may be single images or scripts that stop Firefox and Jmeter from considering a page as completely loaded, but the Browser may already display what appears to be an actually complete page. It is important to determine if that time is consistently below the machine measured time. HTH, Felix --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
