You are on page 1of 8

White Paper

Zeus Traffic Manager VA Performance on vSphere 4

Zeus. Why wait…

.......... Zeusbench produces similar results to those that would be achieved with other benchmarking tools....................................................... .................................0 and outlines the methods used to achieve these performance figures.............. a high-performance.. 7 Introduction This document details the performance figures obtained by the Zeus Traffic Manager Virtual Appliance (Zeus Traffic Manager VA) on VMware vSphere 4........com/articles/2009/03/26/introducing_zeusbench Z e u s Tr a f f i c M a n a g e r V A P e r f o r m a n c e o n V M w a r e v S p h e r e 4 Page 2 of 8 Zeus............... 3 Virtual Appliance ................ 4 Results............................................................ These results were then collated to ascertain the overall performance of the system under test................................................................ Why wait............................................................................... HTTP benchmarking tool included with Zeus Traffic Manager............................... 6 Analysis .............. vendor agnostic.......................... 3 Hardware .... along with the system under test..... generated requests and sent them to the system under test................. which consisted of 64-bit dual-core CPU machines running Linux.............. 1 http://knowledgehub.............................. such as Apachebench....................................................................... 3 Native Software........................ Test Setup A series of clients and web servers...................... switched Ethernet network using multiple 1Gbps NICs.......and quadcore CPU machines also running Linux........................................................ A comparison of the performance of various virtual appliance configurations relative to that of the native install of Linux on the same hardware is also provided......................... were connected to a flat....... which consisted of 64-bit dual.......zeus.............................. 3 Benchmarks ............................................................................................. The requests were generated by a program called Zeusbench 1.............................. The clients.... Zeusbench reported the benchmarking results obtained on each of the clients......................................................................................... 2 System Under Test........ Zeus Traffic Manager was running on the system under test and load balanced the requests across the web servers......................................Contents Introduction ........................................................................................ 2 Test Setup ..............

Only the Intel Pro 1000VT interfaces were used to conduct the benchmarks.. . The “vmxnet3” network device was used for each of these virtual network interfaces. Each of the four Intel Pro 1000VT network interfaces was configured on a separate virtual network and added to the virtual machine. The network interfaces are broken down into four Intel Pro 1000VT interfaces and two interfaces built in to the motherboard. VMware tools are preinstalled in the Zeus Traffic Manager VA image.0 running on the system under test. All non-essential services were stopped and the following Linux kernel tunings applied: # Increase local port range echo "1024 65535" > /proc/sys/net/ipv4/ip_local_port_range # Disable syncookies echo 0 > /proc/sys/net/ipv4/tcp_syncookies # Increase maximum syn backlog echo 8092 > /proc/sys/net/ipv4/tcp_max_syn_backlog # Increase maximum socket backlog echo 1024 > /proc/sys/net/core/somaxconn # Increase maximum available file descriptors echo 2097152 > /proc/sys/fs/file-max Virtual Appliance The performance figures for the various virtual appliance configurations were obtained using a pre-release version of Zeus Traffic Manager VA 5. The virtual machine was allocated 512 MB of RAM and the “vmxThroughputWeight” setting for the ESX server was set to 128. the Zeus Traffic Manager Virtual Appliance under test was the only virtual machine installed on the vSphere server..1r2 virtual appliance configured on vSphere 4.System Under Test Hardware The hardware used to conduct the benchmarks consisted of a Dell PowerEdge 2950 containing an Intel® Quad-Core Xeon® E5450 processor. Z e u s Tr a f f i c M a n a g e r V A P e r f o r m a n c e o n V M w a r e v S p h e r e 4 Page 3 of 8 Zeus.1r1.10 Live CD on the machine and installing on it the Linux x86_64 build of Zeus Traffic Manager version 5. Native Software The performance figures for the native hardware of the system under test were obtained by running a 64-bit Ubuntu 8. with one of the built-in interfaces used for the ESX service console and the other interface remaining unused. When obtaining performance figures. Why wait. No additional tuning was performed beyond that which already exists on the standard Virtual Appliance image. 8GB of RAM and 6 network interfaces.

each on a new connection. A short response is returned from the web server for each request. Each client sends its requests on an existing keepalive connection and SSL session IDs are reused. For each request. Clients send a series of requests to Zeus Traffic Manager. Clients send a series of HTTPS requests. HTTP 8K requests per second: The rate at which Zeus Traffic Manager can handle requests for an 8 KB file. so each connection requires a full SSL handshake. The test measures the performance of the cipher used to encrypt and decrypt the data passed along the SSL connection. Layer 4 requests per second: The rate at which Zeus Traffic Manager can handle short requests and responses. Clients send a series of HTTP requests. HTTP throughput: The throughput that Zeus Traffic Manager can sustain when serving large files via HTTP. The methodology used for the HTTP requests per second benchmark is used here. each on a new connection. SSL connections per second: The rate at which Zeus Traffic Manager can decrypt new SSL connections. HTTP 2K requests per second: The rate at which Zeus Traffic Manager can handle requests for a 2 KB file. Zeus Traffic Manager processes each request and forwards it on to a web server over another keepalive connection. The benchmarks conducted consisted of the following tests: Layer 4 connections per second: The rate at which Zeus Traffic Manager can handle new TCP connections. Each client sends all its requests on the same connection to Zeus Traffic Manager. These figures could then be compared with those obtained for the native system to discover how performance is affected by running Zeus Traffic Manager inside a virtual machine. . The web server responds with a zero sized file. Why wait.Benchmarks The intention of the benchmarks was to obtain performance figures for a 64-bit virtual machines running with 1. for a zero sized file. The web server sends back a response for each request. Each client sends its requests down an existing keepalive connection. The web server sends back a response for each request. 2. each on a new connection. SSL throughput: The throughput Zeus Traffic Manager can sustain whilst performing SSL decryption. 1024 bit RC-4 encryption is used. Zeus Traffic Manager opens a new connection to a web server and forwards the request to it.. 3 and 4 virtual CPUs. Zeus Traffic Manager parses the requests and forwards them on to a web server using an established keepalive connection.. which forwards them over a persistent connection to a web server. HTTP requests per second: The rate at which Zeus Traffic Manager can handle HTTP requests. HTTP connections per second: The rate at which Zeus Traffic Manager can process new HTTP connections. however the files requested are 1 MB in size. Z e u s Tr a f f i c M a n a g e r V A P e r f o r m a n c e o n V M w a r e v S p h e r e 4 Page 4 of 8 Zeus. SSL session IDs are not reused.

.Cache requests per second: The rate at which Zeus Traffic Manager can serve small files directly from its cache. . Cache throughput: The throughput that Zeus Traffic Manager can sustain when serving large files from its cache.. Z e u s Tr a f f i c M a n a g e r V A P e r f o r m a n c e o n V M w a r e v S p h e r e 4 Page 5 of 8 Zeus. Why wait.

63 220000 4.31 202000 3.99 4 vCPU 30200 123000 42600 104000 63000 37000 2. Why wait.71 180000 4 3 vCPU 35300 140000 51100 113000 69200 38500 2.01 1 vCPU 20600 106000 26800 67200 47400 30200 2.97 7790 2..99 The following chart compares the performance of each of the virtual machine configurations against the native hardware performance: Performance as a percentage of native 140% 120% 100% 80% 60% 40% 20% 0% 1 vCPU 2 vCPU 3 vCPU 4 vCPU Z e u s Tr a f f i c M a n a g e r V A P e r f o r m a n c e o n V M w a r e v S p h e r e 4 Page 6 of 8 Zeus.23 8300 2. .73 2350 0.98 6540 2.35 247000 3.933 118000 3..Results The following table presents the raw performance figures for the native hardware running Zeus Traffic Manager and each of the virtual machine configurations running Zeus Traffic Manager VA: Test Name L4 conn/s L4 req/s HTTP conn/s HTTP req/s HTTP 2k req/s HTTP 8k req/s HTTP throughput (GBits) SSL conn/s SSL throughput (GBits) Cache req/s Cache throughput (GBits) Native 28800 134000 43400 110000 75200 44800 3.01 4400 1.99 2 vCPU 28700 128000 38900 95300 64300 38200 3.

.. However these numbers show the advantage of the highly optimized vSphere network stack coupled with a tuned Virtual Appliance. The performance of the 1-vCPU appliances in these benchmarks was quite strong. This is due to the hypervisor using some CPU time to manage the network traffic and virtual machines.vmware. and the need for the vSphere network layer to consume some resource. using a 10Gb network or more 1Gb network cards cache throughput would be higher. This was the maximum network bandwidth available on the SUT. was faster than running on a native installation of Linux. with 25% fewer CPUs it is therefore expected that the performance drops by approximately 25%.Analysis The chart presented above shows the difference in performance between benchmarks for each virtual machine configuration. The SSL connections/second test has a relatively small amount of network traffic and is highly dependent on CPU speed. Performance would normally be expected to decrease when configuring fewer vCPUs for the virtual machine. Cache throughput tests show results consistently at 4Gb/second.0 are approximately 25% better than results obtained on the same System under Test (SUT) using ESX 3. This is likely to be caused by co-scheduling restrictions. Overall. with the service console requiring some CPU time. The results obtained do not show perfectly linear scaling with the number of vCPUs assigned to the virtual machine. The figures obtained.com/pdf/vi_performance_tuning.5 update 4. VMware’s performance tuning guide for ESX2 highlights that running a single-vCPU virtual appliance can have performance benefits over running a multiple-vCPU virtual appliance. Why wait.pdf] Z e u s Tr a f f i c M a n a g e r V A P e r f o r m a n c e o n V M w a r e v S p h e r e 4 Page 7 of 8 Zeus. 2 “Performance Tuning Best Practices for ESX Server 3” (VMware). With the exception of SSL connections/second. The configurations vary by the number of virtual CPUs configured. the results obtained using vSphere 4. Available at [http://www. On production systems running other virtual machines performance figures will scale differently from those obtained here.0 hypervisor. This shows the huge performance improvements in the current vSphere 4. with the average performance the same as native. so if the necessary workload can be met with a single vCPU then it could improve the overall performance of the system when compared with running a multiple-vCPU appliance to cover the same workload. however. Typically with previous generations of hypervisor there would be a performance hit running under a virtual environment. Performance for some configurations and benchmarks. the 3 vCPU configuration obtained the best performance. and SSL connections/second showing the lowest performance at 78% of native. in particular with 3 vCPUs. show that 3vCPUs mostly obtained higher figures than the 4vCPU configuration. .

com or twitter. California 94402 United States of America. TrafficScript.com Stay in touch with Zeus by following: blog.zeus.com Email: info@zeus. (U.zeus.com Email: info@zeus.) 1875 South Grant Street Suite 720 San Mateo. the Zeus logo.com/ZeusTechnology Try before you buy.com Zeus Technology. Phone: 1-888-ZEUS-INC Fax: Web: 1-866-628-7884 www. Zeus Web Server.com/downloads Technical support is also available during your evaluation. please email: info@zeus. All other brands and product names may be trademarks or registered trademarks of their respective owners. All rights reserved.zeus.For further information. Zeus.zeus.zeus.com or visit www. Inc. Zeus Technology Limited (UK) The Jeffreys Building Cowley Road Cambridge CB4 0WS United Kingdom Sales: +44 (0)1223 568555 Main: +44 (0)1223 525000 Fax: Web: +44 (0)1223 525100 www. Zeus Traffic Manager and Cloud Traffic Manager are trademarks of Zeus Technology.com © Zeus Technology Limited 2009. .S. Simply visit our website: www. Zeus Technology.