Skip to main content

Virtualized Web App performs poorly



Seriously if you're an admin, you know there is a lot more to performance than an underlying layer.

Virtualization is the magic wand = wrong
App will live happily ever after = do they now?
I have cron/scheduled tasks jobs running
What about those Virus scanners? Do they know you're benchmarking your VM?
Questions, Questions...

Well anyways this article got analysed by Slashdot users as media continues to thrash VMware's product by running outdated products, beta products and in many cases also beta benchmark tools!

Original article says:

The purpose of this article is to explore the performance impact of virtualization on a web application that uses typical development methodologies. The goal is to give administrators some idea of the performance impact that virtualization will have on their applications as they become loaded - and how it is different from the native servers. For our reference application, we will use the ASP.NET Issue Tracker System, part of the Microsoft ASP.NET Starter Kit. While this sample application is relatively simple, it makes use of one of the most common development frameworks and the code is typical of many larger IT web applications.

We ran 4 load tests on the application. The first measured the performance of the web application running on a native Windows 2003 Server installation. The second test measured the performance of the web application running on a virtual Windows 2003 Server installation running within VMware Server 1.0.1. VMware ran on Linux (CentOS 4.4). The base hardware for both machines is a Dell Poweredge SC1420 with dual Xeon 2.8GHz processors. The virtualized server has the same memory available to it (2G) as the native server (which implies that the physical machine running VMware has more memory). Since the Intel Xeon processor supports hyperthreading, there was some debate as to the impact of hyperthreading on the virtualized machine. So we decided to run two additional tests with hyperthreading disabled for both the native and virtualized servers.


Article was also discussed on Slashdot.
Labels:

Comments

Post a Comment

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
Post a Comment
Read more

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...
Post a Comment
Read more