ab -n 500 -c 150 http://eclass.adzu.edu.ph/index.php
Benchmarking eclass.adzu.edu.ph (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
Completed 400 requests
Finished 500 requests
Server Software: Apache
Server Hostname: eclass.adzu.edu.ph
Server Port: 80
Document Path: /index.php
Document Length: 15396 bytes
Concurrency Level: 150
Time taken for tests: 52.776573 seconds
Complete requests: 500
Failed requests: 0
Write errors: 0
Total transferred: 7905000 bytes
HTML transferred: 7698000 bytes
Requests per second: 9.47 [#/sec] (mean)
Time per request: 15832.972 [ms] (mean)
Time per request: 105.553 [ms] (mean, across all concurrent requests)
Transfer rate: 146.26 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 351 653.3 0 3459
Processing: 792 13070 4636.6 14902 42722
Waiting: 7 13001 4686.9 14843 42687
Total: 844 13422 4456.3 14935 43554
Percentage of the requests served within a certain time (ms)
50% 14935
66% 15285
75% 15472
80% 15538
90% 16061
95% 18304
98% 19877
99% 20590
100% 43554 (longest request)
is my moodle running the optimal? what should i do to lesser the lenght of loading and speed things up for more the number i had benchmark...
Server Software: Apache
Server Hostname: eclass.adzu.edu.ph
Server Port: 80
Document Path: /index.php
Document Length: 14619 bytes
Concurrency Level: 1000
Time taken for tests: 129.842995 seconds
Complete requests: 1000
Failed requests: 0
Write errors: 0
Total transferred: 19727668 bytes
HTML transferred: 19158004 bytes
Requests per second: 7.70 [#/sec] (mean)
Time per request: 129843.002 [ms] (mean)
Time per request: 129.843 [ms] (mean, across all concurrent requests)
Transfer rate: 148.37 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 3 13444 12159.3 10772 57901
Processing: 2316 21139 10392.0 22112 95912
Waiting: 6 12917 6500.7 13544 77109
Total: 9713 34584 14539.6 31746 127594
Percentage of the requests served within a certain time (ms)
50% 31746
66% 35293
75% 36555
80% 38768
90% 55950
95% 72236
98% 76953
99% 76988
100% 127594 (longest request)
It seems my server is dying, can someone explain the result . I takes time to load my site why?
Server Hostname: eclass.adzu.edu.ph
Server Port: 80
Document Path: /index.php
Document Length: 14619 bytes
Concurrency Level: 1000
Time taken for tests: 129.842995 seconds
Complete requests: 1000
Failed requests: 0
Write errors: 0
Total transferred: 19727668 bytes
HTML transferred: 19158004 bytes
Requests per second: 7.70 [#/sec] (mean)
Time per request: 129843.002 [ms] (mean)
Time per request: 129.843 [ms] (mean, across all concurrent requests)
Transfer rate: 148.37 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 3 13444 12159.3 10772 57901
Processing: 2316 21139 10392.0 22112 95912
Waiting: 6 12917 6500.7 13544 77109
Total: 9713 34584 14539.6 31746 127594
Percentage of the requests served within a certain time (ms)
50% 31746
66% 35293
75% 36555
80% 38768
90% 55950
95% 72236
98% 76953
99% 76988
100% 127594 (longest request)
It seems my server is dying, can someone explain the result . I takes time to load my site why?
1000 concurrency? It doesn't make any sense!
yes, its on 1000 concurrent
No doubt about it 
But there is no usage scenario where you would expect your webserver to be hit by 1000 concurrent connections. It is certain that the server will not give any useful service under that kind of connection storm. So... why are you trying this?
I would suggest you read a little bit on Apache benchmarking, and what the different metrics are, and develop a test plan.
I'd also recommend you update to the very latest Moodle 1.4.4+. Up until recently, "ab" (and other benchmarking tools) would get the "database connection refused" page, and thing it was a valid page, not an error page. So ab stats would sometimes appear to be extremely good because the DB was rejecting connections.
But there is no usage scenario where you would expect your webserver to be hit by 1000 concurrent connections. It is certain that the server will not give any useful service under that kind of connection storm. So... why are you trying this?
I would suggest you read a little bit on Apache benchmarking, and what the different metrics are, and develop a test plan.
I'd also recommend you update to the very latest Moodle 1.4.4+. Up until recently, "ab" (and other benchmarking tools) would get the "database connection refused" page, and thing it was a valid page, not an error page. So ab stats would sometimes appear to be extremely good because the DB was rejecting connections.
your right database connection refused when so many concurrent user. I AB my site to 10000 because students login simutaneously around 800 to 900 at the same time.
am i wrong using those numbers? hmmm
am i wrong using those numbers? hmmm
So, 800 to 900 students click login in the exact *same* millisecond? Because that is what you are testing... ;)
Even if you have 1000 students "using" moodle at the same time, you are only dealing with 10 or 20 pageviews per second. Each 'pageview' will hit apache with one request for the page itself (heavy), and a few requests for stylesheet, images, etc, which are generally lightweight. ab is a pretty simplistic tool.
Even if you have 1000 students "using" moodle at the same time, you are only dealing with 10 or 20 pageviews per second. Each 'pageview' will hit apache with one request for the page itself (heavy), and a few requests for stylesheet, images, etc, which are generally lightweight. ab is a pretty simplistic tool.
I see, so how can I increase the number pageviews? any idea?
child pid 18884 exit signal Segmentation fault (11)
this error appear in error log, been earching about it any idea?
thanks martin
child pid 18884 exit signal Segmentation fault (11)
this error appear in error log, been earching about it any idea?
thanks martin