Skip to main content

Parallels disagrees with the benchmark

CNET recently did a performance comparison between Parallels Desktop and VMware Fusion. Surprisingly enough, their benchmark also suffered from unrealistic scenarios and vendor bias.

Pretty much everything about this test is upside down:

* It does not make sense to use an exclusive monster 8-core desktop for benchmarking Windows on Mac. Most people use laptops with 2 CPU cores and 2GB of RAM at most.
* Since Mac OS is the primary OS, it does not make sense to give both cores to a Windows VM that runs Word, Excel and Outlook. Office applications don't benefit from multiple CPUs. Perhaps that's why default configuration of Fusion is a single-CPU VM. Come on – most of the VMmark (server benchmark) workloads run in a single-core VM. Yet, desktop benchmark is run with dual cores – does not make much sense to me.
* It does not make sense to use Vista inside a VM. Most people run XP because Vista license only allows the most expensive Vista SKUs to run inside VM, not to mention application compatibility issues.
* It does not make sense to run QuickTime and Photoshop inside Windows VM. Why use Mac OS in the first place if not for running Mac OS-native multimedia apps?


Read the rest and judge for yourself.

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