> 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)? >> >> > No, not all the way down to 4.6 ms certainly, but to some intermediate > small value. > > Look at this while serving static files: >
Serving static files is very different from having a web framework process dynamic requests. -- 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.
