OpenWebLoad - Web Application Load Testing tool

OpenWebLoad is a web application testing tool which provides real time performance measurement of the application along with WebServer.

Installation in Ubuntu

root@server-82:~# apt-get install  openload
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  openload
0 upgraded, 1 newly installed, 0 to remove and 12 not upgraded.
Need to get 18.6 kB of archives.
After this operation, 90.1 kB of additional disk space will be used.

Once setup is done, here is result of man openload

root@server-82:/home/serveradmin# man openload

       -h
              Header value: Specifies a HTTP request header. You can use this option several times to specify several headers. The sentence is -h followed  by  the
              name of header and the quoted value, separated by spaces. E.g. openload -h User-Agent "MSIE 5.0" mysite.com

       -l
              Time  limit:  number  of seconds. The test will only run for the specified number of seconds. The sentence is -l followed by number of seconds, sepaâ
              rated by spaces. E.g. openload -l 10 mysite.com

       -o
              Output mode: Currently only CSV (comma seperated values) is supported. This is useful for importing the result in a spreadsheet. The fields are: Url,
              Number of clients, TPS (Transactions Per Second), Average response time (seconds), Maximum response time, Total number of requests.

       -v
              Verifier mode: (undocumented)

       -b
              Body request: The test just request body response from the test URL. E.g. openload -b mysite.com

OUTPUT RESULTS
       A description of output results is listing below.

           * MaTps: a 20 second moving average of TPS.
           * Tps: (Transactions Per Second) is the number of completed requests during that second.
           * Resp Time: the average response time in seconds for the elapsed second.
           * Err: the percentage of responses that was erronous, i.e. didn't return a HTTP 200 Ok staus.
           * Count: the total number of completed requests.
           * Total TPS is the average TPS for the whole run, i.e. (Total completed requests) / (Total elapsed time).
           * Avg. Response time: the overall average response time in seconds.
           * Max Response time: the highest response time during this run.
Note: you stop the run by pressing Enter.



 Testing with own Server with time limit of 30 seconds and with 100 clients

root@server-82:~# openload -l 30 http://localhost 100
URL: http://localhost:80/
Clients: 100
Time Limit: 30 sec.
MaTps 2600.00, Tps 2600.00, Resp Time  0.038, Err   0%, Count  2600
MaTps 2587.20, Tps 2472.00, Resp Time  0.040, Err   0%, Count  5072
MaTps 2575.78, Tps 2473.00, Resp Time  0.040, Err   0%, Count  7545
MaTps 2564.31, Tps 2461.08, Resp Time  0.041, Err   0%, Count 10011
MaTps 2560.68, Tps 2528.00, Resp Time  0.039, Err   0%, Count 12539
MaTps 2537.58, Tps 2329.67, Resp Time  0.043, Err   0%, Count 14871
MaTps 2515.92, Tps 2321.00, Resp Time  0.043, Err   0%, Count 17192
MaTps 2491.23, Tps 2269.00, Resp Time  0.044, Err   0%, Count 19461
MaTps 2457.81, Tps 2157.00, Resp Time  0.046, Err   0%, Count 21618
MaTps 2450.02, Tps 2380.00, Resp Time  0.042, Err   0%, Count 23998
MaTps 2442.62, Tps 2376.00, Resp Time  0.042, Err   0%, Count 26374
MaTps 2438.52, Tps 2401.60, Resp Time  0.041, Err   0%, Count 28778
MaTps 2420.24, Tps 2255.74, Resp Time  0.044, Err   0%, Count 31036
MaTps 2405.31, Tps 2270.92, Resp Time  0.044, Err   0%, Count 33316
MaTps 2406.99, Tps 2422.16, Resp Time  0.041, Err   0%, Count 35743
MaTps 2409.65, Tps 2433.57, Resp Time  0.041, Err   0%, Count 38179
MaTps 2405.99, Tps 2373.00, Resp Time  0.042, Err   0%, Count 40552
MaTps 2406.69, Tps 2413.00, Resp Time  0.041, Err   0%, Count 42965
MaTps 2391.92, Tps 2259.00, Resp Time  0.044, Err   0%, Count 45224
MaTps 2389.03, Tps 2363.00, Resp Time  0.043, Err   0%, Count 47587
MaTps 2387.09, Tps 2369.63, Resp Time  0.042, Err   0%, Count 49959
MaTps 2383.88, Tps 2355.00, Resp Time  0.042, Err   0%, Count 52314
MaTps 2384.19, Tps 2387.00, Resp Time  0.042, Err   0%, Count 54701
MaTps 2388.27, Tps 2425.00, Resp Time  0.041, Err   0%, Count 57126
MaTps 2385.04, Tps 2356.00, Resp Time  0.042, Err   0%, Count 59482
MaTps 2384.64, Tps 2381.00, Resp Time  0.042, Err   0%, Count 61863
MaTps 2377.38, Tps 2312.00, Resp Time  0.043, Err   0%, Count 64175
MaTps 2372.07, Tps 2324.35, Resp Time  0.043, Err   0%, Count 66504
MaTps 2375.17, Tps 2403.00, Resp Time  0.042, Err   0%, Count 68907
Total TPS: 2296.67
Avg. Response time:  0.042 sec.
Max Response time:   0.199 sec
Total Requests:   68907
Total Errors:         0


When i do test with 10,000 clients, i found total 152 apache process was running. That is why because of M2M worker module of apache. Here is default config portion of apache2.conf

<IfModule mpm_worker_module>
    StartServers          2
    MinSpareThreads      25
    MaxSpareThreads      75
    ThreadLimit          64
    ThreadsPerChild      25
    MaxClients          150
    MaxRequestsPerChild   0
</IfModule>

Initially the apache start with 2 process and reach upto MaxClients limit of 150. So if you want to tweek apache for heavy load then you should increase with these values.

You can get running process with following commands

= ps -aux | grep apache2 | wc -l
or
pgrep apache2 | wc -l

Here apache2 is the process name.