On Tue, Nov 26, 2013 at 9:32 PM, Anthony <[email protected]> wrote:
>
>>> 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)?
>
>
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 500 files with different concurrency.
Concurrency Level: 1
Time taken for tests: 0.288 seconds
Complete requests: 50
Failed requests: 0
Write errors: 0
Total transferred: 2711700 bytes
HTML transferred: 2692300 bytes
Requests per second: 173.85 [#/sec] (mean)
Time per request: 5.752 [ms] (mean)
Time per request: 5.752 [ms] (mean, across all concurrent requests)
Transfer rate: 9207.35 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 1 1 0.2 1 2
Processing: 4 5 1.0 4 8
Waiting: 1 2 1.1 2 6
Total: 5 6 1.0 5 10
WARNING: The median and mean for the processing time are not within a
normal deviation
These results are probably not that reliable.
Percentage of the requests served within a certain time (ms)
50% 5
66% 6
75% 6
80% 6
90% 7
95% 8
98% 10
99% 10
100% 10 (longest request)
and
Concurrency Level: 25
Time taken for tests: 0.049 seconds
Complete requests: 50
Failed requests: 0
Write errors: 0
Total transferred: 2711700 bytes
HTML transferred: 2692300 bytes
Requests per second: 1020.26 [#/sec] (mean)
Time per request: 24.504 [ms] (mean)
Time per request: 0.980 [ms] (mean, across all concurrent requests)
Transfer rate: 54036.05 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 1 4 3.8 2 15
Processing: 7 17 7.6 18 34
Waiting: 1 9 6.8 6 23
Total: 9 21 7.7 23 36
Percentage of the requests served within a certain time (ms)
50% 23
66% 26
75% 27
80% 27
90% 30
95% 35
98% 36
99% 36
100% 36 (longest request)
I feel things will get much better once I optimize table definitions.
> 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 a topic in the
> Google Groups "web2py-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/web2py/rH1C7iXMPNA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
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.
