> > >> ab -n 50 -c 1 [url] >> >> > Concurrency Level: 1 > Time taken for tests: 5.791 seconds > Time per request: 115.813 [ms] (mean) > Time per request: 115.813 [ms] (mean, across all concurrent > requests) >
> ab -n 50 -c 25 [url] >> >> Concurrency Level: 25 > Time taken for tests: 3.461 seconds > Time per request: 1730.347 [ms] (mean) > Time per request: 69.214 [ms] (mean, across all concurrent requests) > In both cases above, 50 requests were completed. In the case of concurrency=25, however, the 50 requests were completed faster (i.e., 3.46 seconds vs. 5.79 seconds in the serial case). So, with concurrent requests, the time per request dropped from 115ms to 69ms. Did you expect it to drop all the way down to 4.6ms (i.e., 115/25)? Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
