Skip to main content

Virtualization Scalability Comparison by LRI, France




More researchers and papers springing up. Latest conducted by " Laboratoire de Recherche en Informatique" This one concludes with the following:

The evaluation of machine virtualization tools is a difficult exercise. We first motivated the use of microbenchmark to better understand the scalability limitations and merits of virtualization tools. We have described a set of metrics (overhead, linearity and isolation), and related microbenchmarks for the CPU, memory, disk and network resources. These metrics allow testing many aspects of these systems, performance as well as usability. We have compared 4 virtualization tools using this methodology: VMware, UML, Vserver and Xen. We clearly noticed strong limitations with VMware and UML, as previously published by other authors, but we have provided a detailed evaluation, identifying overhead, linearity and performance isolation limitations for all machine resources. Vserver and Xen clearly provide the better performance. However, there is still room for improvements in Vserver and Xen, since they do not provide performance isolation for the network between VMs (which is desirable for some users) and Xen suffers from low intervirtual machine communication performance. A significant limitation of Vserver is that it cannot run kernels for guest virtual machines different to the hosting one. But, compared to Xen, its architecture saves a lot of memory space when running many virtual machines, since only one kernel is shared by all VMs. VMware has the advantage of providing performance isolation for all resources. It also allows running unmodified guest OS at the cost of a high overhead and poor linearity with respect to scalability. According to their current respective merits and limitations, the compared VM technologies will match efficiently different application scenarios depending on their need in guest OS configuration, performance isolation and scalability. VMware clearly fits scenarios requiring small number of VMs and performance isolation between VMs. Such scenarios are likely to occur for Grid servers ensuring QoS from service level agreement (SLA). In addition, VMware accepts dynamic instantiation of user defined runtime environment, including specialized OS. Xen will match scenarios where many users or applications are deployed, possibly on ported OSes, on the same hardware with a ”best effort” or opportunistic like QoS (the performance of every VM will depend on the workload of the others). Vserver will accommodate more VMs and provide high performance communication between the VMs. But application should be compliant with the VM hosting kernel. Vserver will match for example scenarios where the number of physical nodes running a distributed application with a fixed number of processes may evolve from time to time. UML is the only one which can be runned by an unprivileged user. Altogether we believe that 1) the result of this study will help users to select the VM technologies corresponding to the characteristics of their application and 2) the proposed metrics and benchmarks could help the VM designers by evaluating their technology with a third point of view (close to user needs), between real applications and low level VM mechanisms benchmarks.


Here's the complete doc.

Update:

John added that this March 2006 paper is doing a scalability comparison on Workstation 3 and GSX server. Both products are outdated so they may not apply to the current product line of VMware.

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!