it's quite common for the browser to take seconds to render the page, if there's deeply nested tables or other fancy layouts. Back when I did webUI stuff, we had to tune the HTML, so the page rendering wasn't horribly slow.
peter On 3/23/06, Massimo Forno <[EMAIL PROTECTED]> wrote: > > Hi, > > First of all I would like to thank you for the very fast answer. > > I am sorry for the stupid question: the time to last byte is calculated > from the request to the server and the last byte received or from the > time to first byte to the last byte? > > I am very interested because I have very bad performances, and I am > trying to understand if it is because the page rendering time > (+javacript time) or just because the server is very slow in the page > processing. > > I am asking that because the results I have got from jmeter are very > good (about 500ms per the heavier page) but using my web application > (with Mozilla + Fasterfox) I get 5 - 6 sec for the same page. > > Thank in advance. > > Massimo. > > > -----Original Message----- > From: Peter Lin [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 23, 2006 2:26 PM > To: JMeter Users List > Subject: Re: JMeter results > > the response time is time to last byte and the 90% line is hte 90th > percentile. > > peter > > On 3/23/06, Massimo Forno <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > > > > I would like to know what kind of results jmeter can display after a > web > > test session, in particular if the response time is calculated as Time > > To First Byte (TTFB), Time To Last Byte (TTLB) and if the 90% Line can > > be considered as a 90th percentile. > > > > > > > > Thank in advance. > > > > > > > > Massimo Forno. > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
