by
Jeroen van de Kamp
Wow, this took a little longer than expected. No.. actually this actually took a lot longer. Ruben Spruijt and I can finally announce the official release of the Project VRC Phase II white paper. This is the biggest release so far and is now available on Projects VRC’s dedicated website www.virtualrealitycheck.net.
This white paper focuses on Terminal Server workloads running on the latest generation Intel processor: the Xeon 5500 series (Nehalem). We did things a bit differently this time, as we now chose to publish the results of the big three hypervisors in a single paper. Ruben and I hope you will find this interesting, even though it should not come as a surprise that Intel’s Nehalem is a fantastic performer with virtualized TS workloads. (Although we still feel we have a couple of interesting angles.)
In this paper we tested Terminal Server 2003 (x86 an x64) workloads on the latest hypervisors from Citrix, Microsoft and VMware with the latest version of the Login VSI benchmark. We also discussed the impact of Office 2007 SP2, Internet Explorer IE7 versus IE8, Citrix CPU Fairshare, the impact of the vMMU settings in vSphere, and much more.
On a side note, Ruben and I learned a big lesson for future Project VRC papers: The next papers will not be this big anymore. There are so many interesting things we can investigate and report on, but is logistically too challenging to put so much in single paper. As a result, the next releases of the project VRC white papers should come at a higher interval. The upcoming series will not focus on TS anymore, but completely on VDI. Ruben and I are really looking forward to this as there are many fascinating topics we can investigate. (But more on this in the future.)
For now, Ruben and I hope you enjoy this latest chapter in the VRC story, and we're looking forward to your thoughts and feedback. You can follow Project VRC on twitter: “ProjectVRC”, “TheJeroen” & “rspruit”.
(Note: You must be logged in to post a comment.)
If you log in and nothing happens, delete your cookies from BrianMadden.com and try again. Sorry about that, but we had to make a one-time change to the cookie path when we migrated web servers.