one thing to keep in mind is jmeter uses one single thread to get the page and all it's resources (when the box is checked).
A browser on the otherhand will use 2 or more threads depending on the protocol. If it is using http1.0, the official spec limits each browser to 4 concurrent connections. Http1.1 limits it to 2 concurrent connections. That means after a browser parses the HTML and extracts all the references to images and other embedded resources, it launches the correct number of threads to fetch all the files. you may want to add performance measurements to your webpage to see how long it takes to process the different parts of a page. peter On Fri, 9 Jul 2004 17:51:16 +0530, Manoj Panicker <[EMAIL PROTECTED]> wrote: > Dear All, > > I have only begun to discover performance testing and JMeter usage. I fail > to understand why JMeter does not face problems as a user does when testing > a site through the browser. I mean I am testing a site where I am facing > performance problems with just 10 live users! But JMeter goes okay with even > 300+ users for the same site. I am running the functional mode and am > collecting all data. Please clarify if I am missing something obvious in > understanding testing...especially with JMeter. > > Best Regards, > Manoj S. Panicker > > Direction Software Solutions > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
