What’s the impact of Microsoft Office on VDI?
I regularly get questions from customers what the impact is of the Microsoft Office version on their VDI deployment. It’s a common misunderstanding that the sizing and performance of a VDI deployment is equal when using Microsoft office 2007, 2010 or 2013.
But until now this was based on a feeling compared with different customers running different Microsoft office versions.
Today, at TechEd Europe 2013 in Madrid Spain, Project VRC published phase 6 of their Virtual Reality Check which addresses the impact of Microsoft Office in a VDI environment.
The goal of this new white paper was to investigate and document the VDI performance impact of Microsoft Office 2013 in comparison to the previous two versions of Microsoft Office, 2007 and 2010. The comparison of Office 2007 with Office 2010, showed only a 1% performance difference in favour of Office 2007. The comparison of Office 2007 and Office 2013 showed a significant performance decrease of over 20%. This leads to the conclusion that to maintain the same performance levels with the newest version of Microsoft Office, about 20% more infrastructure capacity may be needed. Office 2013 also consistently uses more CPU and over 272% more memory than Office 2007. In comparison, Office 2010 only uses 26% more memory. Optimizations such as turning animations and hardware graphics acceleration off did not influence the performance in any way.
Another key finding published in the white paper is that running x64 versions of Windows and Office will have substantial impact on Storage IOPS and memory footprint in comparison to x86 versions.
If you want to know the details, you can download the whitepaper at the Project VRC website.
- Using VMware and Veeam? Update VBR 9.5 to Update 3a now by Edwin Weijdema
- Add Veeam to a Workgroup, Domain or Forest? by Edwin Weijdema
- 20 Years VMware - Past to Present by Alex Muetstege
- Health check your vSphere environment using Runecast… by Erik Scholten
- So Cloud Automation Services are here, what's next?… by Dimitri De Swart