you arent factoring in that you are running 200 threads in parallel. 1681 transactions per second for 200 concurrent requests works out to 1681/200 = 9 requests per second per thread. which means 1000/9 milliseconds per request(assuming no delays) about 111 ms on average (118 in your case)
regards deepak On Mon, Oct 10, 2011 at 4:20 PM, E S <electric.or.sh...@gmail.com> wrote: > I'm seeing some results in the Summary Report listener that doesn't > really make sense to me. The test runs 200 concurrent users all > requesting the same resource for 60 seconds. Here are the Summary > Report Listener results: > > Num requests: 101243 > Average: 118 > Min: 5 > Max: 27743 > Std dev: 349 > Error: 0% > Throughput: 1681/sec > KB/sec: 8210 > Average bytes: 5000 > > It says the throughput is 1681 transactions per second. This seems to > make sense since 101243 / 60 = 1687. However, this means that on > average each transaction should take about 1/1681 * 1000 = 0.59 ms. It > makes sense to me that each request would take less than 1 ms if you > are doing more than 1000 transactions per second. However, the minimum > transaction time listed is 5 ms. Can someone explain this to me? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jmeter-user-unsubscr...@jakarta.apache.org > For additional commands, e-mail: jmeter-user-h...@jakarta.apache.org > >
