>shall we consider 55 requests sent to the server ( 5 Threads * >11(Number of subrequests)) and use this number to calculate the throughput and >Avg. res time? Usually no. The request normally refers to the number of pages a user sees. However since the Request Embedded downloads resources serially without the use of a cache , the throughput values will be worse than it actually is. Adding a CacheManager should improve your values (and is more realistic) .
There are other threads in this forum where felix, sebb and others have provided their input , go through them.. >otherwise it hardly reaches 14 requests per minute. For your example you havent really generated load , throughput values should increase with greater number of threads till it plateaus out and finally falls. regards deepak On Mon, Nov 15, 2010 at 11:18 PM, Amit <[email protected]> wrote: > Hello, > There is an option "Retrieve All Embedded Resource From HTML files" when > configuring "HTTP Request HTTP Client". > > Now in my case, one page request corresponds to ~11 requests sent to the > server > for fulfilling the CSS,JS and images required for that page. > > > In case of load testing the page let's say with 5 Threads and Ramp up of > 2.5 > seconds, shall we consider 55 requests sent to the server ( 5 Threads * > 11(Number of subrequests)) and use this number to calculate the throughput > and > Avg. res time? If I consider 55 request throughput comes in acceptable > limits > and otherwise it hardly reaches 14 requests per minute. > > > At the moment JMeter shows the Avg. Res Time and calculates the throughput > based > on number of threads. > > > The site is hosted on Apache WS 2.2.17 and developed in PHP. > > Appreciate your insights and thoughts on this. > > Regards, > Amit > > > >
