An interesting article from Gartner Analysts. I know I’ve been involved in many projects over the years which touch upon most of these issues at some point. The benefit of hindsight :)
-
Tags
Categories
Archives
- Log in with
.NET Development on a Mac – Fusion or Parallels?
I’ve been recently issued with my first Mac for work, and have been in the process of setting it up as my dev machine. I’m familiar with using Mac’s in several roles over the years, but resisted using one day-to-day until now. I’ve got the base level Macbook Pro (2.26mhz, upgraded to 4gb ram).
Among other apps, I need to run Visual Studio 2008 and SQL Server 2008. Using Bootcamp crossed my mind, but I didn’t like the the idea of rebooting into Windows every time I wanted to look at something dev-related.
So, I downloaded the trial of VMWare Fusion 2.05, installed a shiny new copy of Windows 7 Pro, installed VS2008 Pro, SQL2008, ReSharper, etc, and prepared to be amazed by my new efficient setup.
In short, it was pretty painful – everything just seemed to lag. I was expecting it to be a bit slower than running natively, but after 20 minutes I realised it just wasn’t going to work. I googled to see if this was a common experience, and came across this fairly comprehensive comparison between Fusion and Parallels which concludes “Parallels Desktop is the clear winner running 14-20% faster than VMware Fusion”. That’s an impressive difference on any benchmark!
One very nice feature of both Fusion and Parallels is that you can import the competitor’s virtual image into the other. So after reading this comparison, I figured I had nothing to lose – the next option was to just set up in Bootcamp which still wasn’t appealing. I downloaded and installed Parallels 4, imported my Fusion virtual image, and 20 mins later I booted up the new Parallels image.
This was exactly what I was hoping for – the experience was vastly superior. No obvious lag when opening/closing programs, responsive, didn’t slow down my other Mac programs at all, and just slicker. Build times of existing VS projects may be a bit slower than running natively (understandable given only one cpu core is allocated to the virtual OS – I think), but overall it feels pretty snappy, and definitely not slow to the point I’d bother rebooting into Bootcamp. It’s worth pointing out that I allocated 2gb memory (of 4gb total) to running each Fusion and Parallels – so they were on a fairly level playing field.
Parallels: 1 – Fusion: 0
