Skip to main content

VMmark builsd 1.0 ready for benchmarking!



In order to produce the benchmark, VMware has avoided the relatively easy approach of measuring the performance of virtual applications software running on specific machines. Instead, the benchmark measures the scalability of heterogeneous virtualised workloads. According to VMware: "It provides a consistent methodology so benchmark results can be compared across different virtualisation platforms."

The result is that, by using the benchmark, companies should be able to "make appropriate hardware choices, and compare the performance and scalability of different virtualisation platforms", VMware says.


Nice stuff this benchmarking. But will the clients really benchmark their stuff. Or lwetm e put it more bluntly, how the heck are you going to tell a client/customer to benchmark if they just have no clue of why a benchmark is done in the first place. Now that will not mean that all the clients are that way. I am pretty sure that besides silencing folks who have run tests/benchmarks on their own on the web, it will help VMware respond with the "did you use VMmark for it?". So once again besides the cosmetic response to a Gung-ho tester, it surely will help customers do "some kind of testing" before they start deploying VMware in their organizations. And obviously hats off to the VROOM! team!

Article here.
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