Citrix XenApp Scalability v2015 – Part 1
It’s time to talk about one of my favorite subjects again: scalability.
And what I really mean by “scalability” is single server scalability (SSS) of XenApp or RDSH-based workloads. If you haven’t read my first couple of articles on XenApp Scalability (Part 1 and Part 2), I highly recommend it, so you’re not lost when I’m talking about CPU over-subscription ratios and NUMA. Because that was sooo 2 years ago.
Today we’re going to revisit CPU over-subscription and talk about a new concept called “Cluster on Die” and how that impacts XenApp scalability.
CPU Over-Subscription –> 1.5x or 2x?
If you read those scalability articles from 2013, you saw that I recommend “1.5x” or 150% CPU over-commitment for XenApp workloads. The only way to determine the optimal CPU over-subscription ratio is to test all the variations with a tool such as LoginVSI. But if you don’t have time to test, then 1.5x is a pretty good “sweet spot” in terms of risk and performance.
Read the entire article here, XenApp Scalability v2015 – Part 1