ZEN NETWORKS 3300 PERFORMANCE BENCHMARK SOFINTEL IT ENGINEERING, S.L.

Transcription

1 ZEN NETWORKS 3300 SOFINTEL IT ENGINEERING, S.L. MAY 2014

2 Table of Contents 1 Benchmark scenario Benchmark cases HTTP Profile with HTTPS Offload Listener, 1k key ssl certificate with RC4-SHA algorithm (stronger cipher) HTTP Profile with HTTPS Offload Listener, 1k key ssl certificate with ECDHE-RSA- AES256-GCM-SHA384 algorithm (weaker cipher) HTTP Profile with HTTPS Offload Listener, 2k key ssl certificate with RC4-SHA algorithm (stronger cipher and higher key) HTTP Profile with HTTP Listener L4xNAT Profile with HTTP Protocol Results sumary Page 2 of 13

3 1 Benchmark scenario The scenario applied consists in 3 connected networks via the hardware appliance. The networks are defined as follows: 1. Management Network: /24 Eth0: in 2. Service Network: /24 Eth1: in Client: Backends Network: /24 Eth2: in Backend: The provides a ZenLB EE 3.04 version with a CPU Intel Core i5 660 (2 cores with HT) 3.33G and 4 GB of RAM DDR3. The client and backend hosts have not been overloaded along the benchmark tasks. The client side process used is ab v2.3 (ApacheBench) that will run a big amount of web requests directly to the load balancer. The backend is configured with a simple but powerful web server end called httpterm v1.7.2, which will receive the client requests and will return back an empty web page (0 bytes). Page 3 of 13

4 2 Benchmark cases 2.1 HTTP Profile with HTTPS Offload Listener, 1k key ssl certificate with RC4- SHA algorithm (stronger cipher) Farm Configuration: Farm Profile: HTTP Modified Farm Parameters: Executed command in Client host: Number of working threads: 2000 Farm Listener: HTTPS Ciphers: Custom Security Customize your Ciphers: RC4 SHA Farm Virtual IP and Virtual Port: :443 Key certificate used: 1k # ab n c This command runs 20,000 requests with a 10,000 of concurrent active connections. The result is shown below: Server Software: Server Hostname: Server Port: 443 SSL/TLS Protocol: TLSv1.2,RC4 SHA,1024,128 Document Path: / Document Length: 0 bytes Concurrency Level: Time taken for tests: seconds Complete requests: Failed requests: 0 Total transferred: bytes HTML transferred: 0 bytes Requests per second: [#/sec] (mean) Time per request: [ms] (mean) Time per request: [ms] (mean, across all concurrent requests) Transfer rate: [Kbytes/sec] received Connection Times (ms) min mean[+/ sd] median max Connect: Processing: Waiting: Total: Percentage of the requests served within a certain time (ms) 50% % % % 6624 Page 4 of 13

5 90% % % % % 7954 (longest request) CPU usage in Zen Load Balancer: Meanwhile the test is running the CPU usage in the is used as follows: As it's shown, the CPU never reaches the 100% of its usage. The requests are SSL offloaded smoothly. 2.2 HTTP Profile with HTTPS Offload Listener, 1k key ssl certificate with ECDHE- RSA-AES256-GCM-SHA384 algorithm (weaker cipher) Farm Configuration: Farm Profile: HTTP Modified Farm Parameters: Executed command in Client host: Number of working threads: 2000 Farm Listener: HTTPS Ciphers: Custom Security Customize your Ciphers: ECDHE RSA AES256 GCM SHA384 Farm Virtual IP and Virtual Port: :443 Used certificate: 1k # ab n c Page 5 of 13

6 This command runs 20,000 requests with a 10,000 of concurrent active connections. The result is shown below: Server Software: Server Hostname: Server Port: 443 SSL/TLS Protocol: TLSv1.2,ECDHE RSA AES256 GCM SHA384,1024,256 Document Path: / Document Length: 0 bytes Concurrency Level: Time taken for tests: seconds Complete requests: Failed requests: 0 Total transferred: bytes HTML transferred: 0 bytes Requests per second: [#/sec] (mean) Time per request: [ms] (mean) Time per request: [ms] (mean, across all concurrent requests) Transfer rate: [Kbytes/sec] received Connection Times (ms) min mean[+/ sd] median max Connect: Processing: Waiting: Total: Percentage of the requests served within a certain time (ms) 50% % % % % % % % % (longest request) CPU usage in Zen Load Balancer: Meanwhile the test is running the CPU usage in the is used as follows: Page 6 of 13

7 As it's shown, the CPU never reaches the 80% of its usage. The requests are SSL offloaded without stress. 2.3 HTTP Profile with HTTPS Offload Listener, 2k key ssl certificate with RC4- SHA algorithm (stronger cipher and higher key) Farm Configuration: Farm Profile: HTTPS Modified Farm Parameters: Executed command in Client host: Number of working threads: 2000 Farm Listener: HTTPS Ciphers: Custom Security Customize your Ciphers: RCA SHA Farm Virtual IP and Virtual Port: :443 Used certificate: 2k # ab n c This command runs 20,000 requests with a 10,000 of concurrent active connections. The result is shown below: This is ApacheBench, Version 2.3 <$Revision: $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, Licensed to The Apache Software Foundation, Benchmarking (be patient) Completed 2000 requests Page 7 of 13

8 Completed 4000 requests Completed 6000 requests Completed 8000 requests Completed requests Completed requests Completed requests Completed requests Completed requests Completed requests Finished requests Server Software: Server Hostname: Server Port: 80 SSL/TLS Protocol: TLSv1.2,RC4 SHA,2048,128 Document Path: / Document Length: 0 bytes Concurrency Level: Time taken for tests: seconds Complete requests: Failed requests: 0 Total transferred: bytes HTML transferred: 0 bytes Requests per second: [#/sec] (mean) Time per request: [ms] (mean) Time per request: [ms] (mean, across all concurrent requests) Transfer rate: [Kbytes/sec] received Connection Times (ms) min mean[+/ sd] median max Connect: Processing: Waiting: Total: Percentage of the requests served within a certain time (ms) 50% % % % % % % % % (longest request) Page 8 of 13

9 CPU usage in Zen Load Balancer: Meanwhile the test is running the CPU usage in the is used as follows: As it's shown, the CPU is stable at full load in this case, but the SSL offloaded requests are delivered in a stable response time. 2.4 HTTP Profile with HTTP Listener Farm Configuration: Farm Profile: HTTP Modified Farm Parameters: Executed command in Client host: Number of working threads: 2000 Farm Listener: HTTP Farm Virtual IP and Virtual Port: :80 # ab n c This command runs 40,000 requests with a 20,000 of concurrent active connections. The result is shown below: Server Software: Page 9 of 13

10 Server Hostname: Server Port: 80 Document Path: / Document Length: 0 bytes Concurrency Level: Time taken for tests: seconds Complete requests: Failed requests: 0 Total transferred: bytes HTML transferred: 0 bytes Requests per second: [#/sec] (mean) Time per request: [ms] (mean) Time per request: [ms] (mean, across all concurrent requests) Transfer rate: [Kbytes/sec] received Connection Times (ms) min mean[+/ sd] median max Connect: Processing: Waiting: Total: Percentage of the requests served within a certain time (ms) 50% % % % % % % % % 2788 (longest request) CPU usage in Zen Load Balancer: Meanwhile the test is running the CPU usage in the is used as follows: Page 10 of 13

11 As it's shown, the CPU never reaches the 75% of its usage. The requests are served without any penalty. 2.5 L4xNAT Profile with HTTP Protocol Farm Configuration: Farm Profile: L4xNAT Modified Farm Parameters: Executed command in Client host: Farm Virtual IP and Virtual Port: :80 # ab n c This command runs 200,000 requests with a 20,000 of concurrent active connections. The result is shown below: Server Software: Server Hostname: Server Port: 80 Document Path: / Document Length: 0 bytes Concurrency Level: Time taken for tests: seconds Complete requests: Failed requests: 0 Total transferred: bytes HTML transferred: 0 bytes Requests per second: [#/sec] (mean) Time per request: [ms] (mean) Page 11 of 13

12 Time per request: Transfer rate: [ms] (mean, across all concurrent requests) [Kbytes/sec] received Connection Times (ms) min mean[+/ sd] median max Connect: Processing: Waiting: Total: Percentage of the requests served within a certain time (ms) 50% % % % % % % % % 1005 (longest request) CPU usage in Zen Load Balancer: Meanwhile the test is running the CPU usage in the is used as follows: As it's shown, the CPU never reaches the 1.2% of its usage. The requests are served without any penalty. Page 12 of 13

13 3 Results sumary Please find in the following table the performance benchmark results for all cases over the hardware appliance: Test Number Connections Concurrency Ciphers Protocols 1 20,000 10,000 RC4-SHA 2 20,000 10,000 ECDHE- RSA- AES256- GCM- SHA ,000 10,000 RC4-SHA 4 40,000 20, ,000 20,000 HTTP Farm with HTTPS Listener HTTP Farm with HTTPS Listener HTTP Farm with HTTPS Listener HTTP and HTTP Listener L4xNAT with HTTP Protocol Asymmetric key size Test time (secs) Page 13 of 13