How many vdi per blade

Deployment Guides. Tech Papers. By Product. Citrix Analytics. Citrix Content Collaboration. Citrix Endpoint Management. Citrix Networking.

Citrix Secure Internet Access. Citrix Secure Private Access. Citrix Service Providers. Citrix Virtual Apps and Desktops. Citrix Workspace. Google Cloud Platform. Third Party Content. The Click-Down Podcast. Tech Zone Live. Document History. Aviso legal. This article provides recommendations and guidance to estimate how many users or virtual machines VMs can be supported on a single physical host.

The idea is to ascertain how many users or VMs can be ran on a single piece of hardware running a major hypervisor such as a Citrix Hypervisor. Hyunju Lee. Views Total views.

Actions Shares. No notes for slide. Software VDI 1. Glenda Canfield 2. Distributed vs. Remote PCs What is the difference? VDI Components VDI User Density Driving Factors What density level will meet user performance targets? Evaluation Criteria Driving Factors What storage configuration meets both desired user performance targets and business e.

Categories of Evaluation Metrics Quantitative What are Workstation Blades Whats the use case If you follow the limits using the VM specifications defined by this organization, you will find the following:.

Now we are within limit ranges for GHz per core and the amount of VM per host. However, we need GB, but only GB is available on those shiny new servers. No matter what they do their CPU power will be underutilized due to the lack of memory resources or the limits imposed by the hypervisor.

I asked myself what I would have chosen for this scenario. Assuming I am not allowed to change the specifications for the virtual desktops I would probably try to bump the CPU clock up to 3. Most vendors, with very few exceptions, have no skilled pre-sales to properly size hardware based on your real requirements. Another possible option would be to add the new blades to the existing server cluster, ignoring the recommendation to isolate desktop workload from server workload.

When mixing both workloads vSphere DRS should quick-in and accommodate the workload. Server and Desktop workloads are inherently different and make cause adverse bottlenecks to each other. Then let me introduce you to LoginVSI. But if you just want a quick and dirty estimate, use the Rule of 5 and 10 and get on with your day!

Now, I have to put on my Consulting hat and cover myself a bit. Because there are actually dozens of variables that influence SSS and 5 and 10 might not be the right multipliers for you and your exact situation. What if your VDI workload calls for developers vs.

Well, in that case, your multiplier might be 2. Selective H. Your multiplier might be 4 in that case. In that case, your multiplier might be 9.

But what if you tune the heck out of your image, optimize with WEM , use selective H. Then your multiplier could be The point is that your mileage will absolutely vary depending on a number of factors. Hopefully this new rule and updated scalability guidance helps you in your travels. Thanks for reading.