Weekly update of the Proxy Reverse plugin and some benchmarks

Hi all, 
 
This week I added trace calls to the main proxy file. Now the work of the proxy can be monitored easier. I also made some minor improvements to the code.

I did a lot of performance tests. I used a dual core virtual machine with one monkey configured to work as a proxy (Locking Round Robin used as a balancer) and three slave servers. As you can see the results are pretty good:

Via proxy reverse:

# siege -b -t10S -c1 ‘http://217.18.244.215/‘ > /dev/null
Transactions:                2944 hits
Availability:              100.00 %
Elapsed time:                9.35 secs
Data transferred:            0.12 MB
Response time:                0.00 secs
Transaction rate:          314.87 trans/sec
Throughput:                0.01 MB/sec
Concurrency:                0.96
Successful transactions:        2944
Failed transactions:               0
Longest transaction:            0.16
Shortest transaction:            0.00

# siege -b -t10S -c2 ‘http://217.18.244.215/‘ > /dev/null
Transactions:                6270 hits
Availability:              100.00 %
Elapsed time:                9.89 secs
Data transferred:            0.25 MB
Response time:                0.00 secs
Transaction rate:          633.97 trans/sec
Throughput:                0.02 MB/sec
Concurrency:                1.69
Successful transactions:        6270
Failed transactions:               0
Longest transaction:            0.10
Shortest transaction:            0.00

# siege -b -t10S -c5 ‘http://217.18.244.215/‘ > /dev/null
Transactions:                4591 hits
Availability:              100.00 %
Elapsed time:                9.28 secs
Data transferred:            0.18 MB
Response time:                0.01 secs
Transaction rate:          494.72 trans/sec
Throughput:                0.02 MB/sec
Concurrency:                2.52
Successful transactions:        4591
Failed transactions:               0
Longest transaction:            0.06
Shortest transaction:            0.00

==== ==== ==== ====

Direct:

# siege -b -t10S -c1 ‘http://217.18.244.215:8080/‘ > /dev/null
Transactions:                4594 hits
Availability:              100.00 %
Elapsed time:                9.36 secs
Data transferred:            0.18 MB
Response time:                0.00 secs
Transaction rate:          490.81 trans/sec
Throughput:                0.02 MB/sec
Concurrency:                0.75
Successful transactions:        4594
Failed transactions:               0
Longest transaction:            0.07
Shortest transaction:            0.00

# siege -b -t10S -c2 ‘http://217.18.244.215:8080/‘ > /dev/null
Transactions:                6298 hits
Availability:              100.00 %
Elapsed time:                9.74 secs
Data transferred:            0.25 MB
Response time:                0.00 secs
Transaction rate:          646.61 trans/sec
Throughput:                0.03 MB/sec
Concurrency:                1.90
Successful transactions:        6298
Failed transactions:               0
Longest transaction:            0.13
Shortest transaction:            0.00

# siege -b -t10S -c5 ‘http://217.18.244.215:8080/‘ > /dev/null
Transactions:                6300 hits
Availability:              100.00 %
Elapsed time:                9.76 secs
Data transferred:            0.25 MB
Response time:                0.01 secs
Transaction rate:          645.49 trans/sec
Throughput:                0.03 MB/sec
Concurrency:                3.49
Successful transactions:        6300
Failed transactions:               0
Longest transaction:            0.21
Shortest transaction:            0.00

 
Next week I’m planning to write some more documentation and I will try to compare it with nginx and will write the results.
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s