Skip to main content

Desktop Virtualization Benchmark Mac OS; No clear winner

This is where those tests were carried out:

When we were choosing computer models, we set out to choose not the fastest, latest models, but ones that would be a good representation of what most people may have. Certainly, the faster models of these computers will perform even better.

Similarly, we had a greater focus on XP simply because it's more prevalent at this point, but we did want to get an understanding of how Vista performed as well.

The baseline PC we used was a brand new Fujitsu Lifebook A6025, with an Intel Core Duo running at 1.86 GHz, 1GB RAM, running Windows XP SP2.

We chose three Mac models to compare alongside a name brand PC: a MacBook, a MacBook Pro, and a Mac Pro.

The MacBook was a 2GB RAM machine, running a 1.83 GHz Core Duo processor. The MacBook Pro was a 4GB RAM machine, running a 2.16 GHz Core 2 Duo processor. And, the Mac Pro was a 4GB RAM machine, running a Quad Core configuration with two 2.66 GHz Dual-Core Intel Xeon processors.

Test Types

There are three kinds of tests that we ran: one step tasks, multi-step task tests, and quantitative benchmarks.

The first set of tests was focused on time to complete one step tasks in Microsoft Office 2007, Internet Explorer, and file/network i/o. These one step tasks mean that from the human point of view, once you clicked a mouse, or key, the test would run to completion without further human interaction. For example, launching applications, scrolling large documents, printing, etc.

The second set of tests were "task tests". These were primarily cross platform, and required multiple steps from beginning to end. These were focused on the interaction between Mac OS X and the virtualization environment. For example, if you were to receive a PDF enclosure in Outlook, and you wanted to open it up in Mac OS X Preview; or you wanted to click on an email link in Safari, and you wanted to use it to create a new email message in Outlook.

The third set of tests are quantitative benchmarks using a utility to test CPU, graphics, disk, etc... In our case, we experimented with Sandra 2007 benchmarks, but found the results to be erroneous and not usable for the virtualization environments. We threw out these results and focused on the first two sets.

For those interested in the benchmarking methodologies, see the more detailed testing information in Appendix A. For the detailed results of the tests used for the analysis, see Appendix B. Both appendices are available on the MacTech web site.





...and according to Arstechnica is didn't really show us a winner, I honestly haven't had the time to do virtualization on Mac extensively :

Benckmark links and Arstechnica link

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