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

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