This article has been update with a 2014 revision. Click here to go to the PVS vs MCS 2014 revision.
Over one and a half year ago I wrote a follow up on an article by Citrix architect Daniel Feller. The original article by Daniel Feller needed an update and now mine is getting pretty outdated as well.
I’m writing this in such a way you won’t be needing to read the earlier articles but of course you are free to do so anyway.
The first article by Daniel Feller can be found here.
My article called Provisioning Services vs Machine Creation Services can be found here.
After Daniel posted his decision tree over two years ago a lot has happened. New Citrix features like XenServer Intellicache and MCS for “XenApp on XenDesktop 7” have been released and are changing the whole decision making process.
On top of that vendors started to work on solving the whole storage IO issue.
If you are reading this you might also be interested in part 1 of the CPU scheduling and memory optimization solutions series.
For a while now customers and colleagues are asking me which tool to use when it comes to CPU scheduling and Memory optimization. We use several management products and end up with more than one product utilizing these tasks. Choice is good but do we just enable them all and if not what’s the best way to configure this?
When you look a little bit deeper then plain and simple marketing you’ll notice that the way the different products handle memory optimization totally different and combining some of them will degrade system performance or might not work.
To start off I will first try to explain how each product works and will then summarize and see if we can work through them and work to a proper advice.