Skip to main content

SPEC on Virtualization Benchmark



AS you can see that VMware is the only Virtualization vendor participating in the committee. The way I read it, its still in the beginning phase.


The group is investigating the use of heterogeneous workloads that are spread across multiple virtual machines on a single server. A key aspect will be defining a methodology to model the dynamic nature of customer workloads in this environment.

SPEC will use its current worldwide standard benchmarks as the basis for generating workloads that are typical of server use. The methods and metrics used by the benchmark will be defined as part of the working group's efforts.

SPEC expects that a wide range of computer server manufacturers, systems integrators, and virtualization software vendors will run the benchmark and report results. Data from running the benchmark tests is targeted for use by IT professionals and decision makers throughout the industry interested in using virtualization to reduce costs and ease IT infrastructure management.


Well Benchmarking is a really different ballgame. To reach an acceptable level of maturity (something like TPC), it will take quite sometime. SWsoft has called in the past of various benchmarking needs and by joining the bandwagon in this committee we , as users, hope to get some real results.

And I agree with Richard here...

How much more time? Probably years, said Richard Fichera, Hewlett-Packard director of blade system strategies, who in previous role as an analyst, worked with vendors attempting to develop the benchmark. "It's such a quagmire," he said. "It's going to be a long time before you see a 'TPC-v'."


Anyways , as Steve puts in, all this will help us achieve a really scalable and high performing Virtualization solution. I have posted some of the "alleged" tests/ benchmarks in my older blogposts but its time to move towards something really robust!

I still dream of doing a performance benchmarking of an Oracle RAC or some other load balanced cluster on VMware. Imagine, 4 quad-core boxes, 1 TB RAM, and 64 node Oracle RAC (sorry I'm stuck on the Oracle RAC until I find something equally attractive ;)). Won't that be awesome!

Here's a link to SPEC.
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