Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
1–10 of 40 posts
Re: Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
#2Is this in the nginx config? Can anybody elaborate a bit further? Here is what I am currently using in my nginx config for ssl:
ssl_session_cache shared:SSL_CACHE:8m;
ssl_session_timeout 5m;
# Mitigate BEAST attacks
ssl_ciphers RC4:HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;Re: Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
#3> I had the wrong ciphers configured. After some quick tweaking and a confirmation using openssl s_client -connect server:ip Is this in the nginx config? Can anybody elaborate a bit further? Here is what I am currently using in my nginx config for ssl: ssl_session_cache shared:SSL_CACHE:8m; ssl_session_timeout 5m; # Mitigate BEAST attacks ssl_ciphers RC4:HIGH:!aNULL:!MD5; ssl_prefer_server_ciphers on;
Re: Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
#4Re: Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
#5> I had the wrong ciphers configured. After some quick tweaking and a confirmation using openssl s_client -connect server:ip Is this in the nginx config? Can anybody elaborate a bit further? Here is what I am currently using in my nginx config for ssl: ssl_session_cache shared:SSL_CACHE:8m; ssl_session_timeout 5m; # Mitigate BEAST attacks ssl_ciphers RC4:HIGH:!aNULL:!MD5; ssl_prefer_server_ciphers on;
openssl s_client -host localhost -port 8082
Which is a openssl command. These settings were used for testing SSL: https://github.com/observing/balancerbattle/blob/master/ngin...See https://gist.github.com/3rd-Eden/5345018 for the output of the openssl s_client for those ciphers. You'll see that `cipher : RC4-SHA` is used here. Which is one of the fastest if not the fastest cipher available.
Re: Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
#6How many requests are made per connection? In order to better gauge performance we need a 3-axis plot, where the response rate is measured against various request-per-connection values and connection rates.
source: https://github.com/observing/balancerbattle#benchmarking
Re: Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
#7From an operations standpoint, haproxy has other features (failover, cli management, clustering) that actually makes it a much better load balancer. I usually install all three haproxy, stud, nginx because they are each very good in their specific niche. As for the simplicity of installation, that can be handled with a configuration manager.
Re: Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
#8What the option does is close the connection between the proxy and the backend so that HAProxy will analyse further requests instead of just forwarding to the already established connection.
To be fair, I don't know what nginx does - whether connections are kept open or shut down - so I'm not sure that it'd be a fair comparison.
Also interesting are the HAProxy built in SSL times. I'm surprised they're so slow. Perhaps the cipher is also the culprit. The cipher can also be specified in HAProxy.
bind *:8080 ssl crt /root/balancerbattle/ssl/combined.pem ciphers RC4-SHA:AES128-SHA:AES:!ADH:!aNULL:!DH:!EDH:!eNULLRe: Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
#9Re: Balancer Battle – Load testing HAproxy, Nginx and HTTP-Proxy's WebSocket support
#10Why do people always benchmark on virtual machines running on someone else's server, and expect meaningful results?
You need to have multiple (powerful) machines for this. And also, spinning up machines in the cloud is quite easy to do and allows people to reproduce the same test results because you have access to exactly the same environment.