One Size Does Not Fit All: vGPU Profiles
By CMD Technology Group
3 min read
In our previous HDX blog post, we explored the intersection of Citrix Virtual Desktops and HDX 3D Pro with NVIDIA Virtual GPU (vGPU).
Where HDX 3D Pro affords 3D graphics users the power of a GPU in their virtual desktop, NVIDIA vGPU allows multiple virtual machines simultaneous access to a single physical GPU.
Can Performance Sacrifice Be Avoided?
By sharing a GPU among multiple workloads, questions arise around scalability and performance. How do we achieve cost-effective scalability without sacrificing the graphics performance of our VDI sessions?
The Role of Profiles
With advancements in virtual desktop hosting, administrators have been able to scale performance while customizing user experience. NVIDIA vGPU profiles provide an opportunity to address both. Profiles serve as a framework for allocating fixed share resources to each virtual machine (VM) from the total pool of memory available – all based on user needs.
Profiles Dependency On GPU and License Edition
As GPUs have different features and resources, they also support different profiles types. The chosen GPU dictates the profiles available. The selected NVIDIA software license edition also unlocks specific profiles.
When determining a vGPU profile type, there are a few key questions to ask of your use case:
Profile Naming Conventions
NVIDIA vGPU profile names indicate answers to the above questions. Let’s take a closer look at the Tesla series M6 GPU accelerator. Examining the M6–1B profile, we know:
Profiles provide structure for how a GPU is shared among multiple VMs. Profiles directly impact the number of machines each host can scale to. Sizing exercises aid in planning your deployment.
Let’s take the example using the M6 further.
M6An M6 graphics card has a total of 8 GB of frame buffer and one physical GPU per board.
*profiles are further classified by the number of supported monitors and maximum resolution
As mentioned, the M10 graphics card has a total of 32 GB of frame buffer. It contains 4 GPUs with 8 GB of frame buffer available to each GPU.
Profile types can vary per board but must stay the same per GPU. For example, one GPU may apply a 1Q profile, while another a 4Q profile. In this scenario, GPU (0) fits 8 VMs with 1 vGPU each. GPU (1) accommodates 2 VMs with 4 vGPU each. A different profile could be applied to GPU (3) and GPU (4).
When sharing 32 GB of frame buffer among GPUs on a single physical M10 card, frame buffer must be allocated in divisible factors (i.e., 1, 2, 4, 8) across GPUs with one profile per GPU. Mixing profiles allows administrators the flexibility to serve multiple use cases with a single graphics card.
When sharing a single GPU among multiple machines, vGPU profiles are critical. The number of machines each host can accommodate is directly affected by the vGPU profile, and in turn, the scale of desktop deployment.
With so many advantages today, graphics-rich VDI should be commonplace. NVIDIA vGPU and HDX 3D Pro offer versatility and performance, without compromising user density.
Get in touch
You can email us at firstname.lastname@example.org
Give us a call at 1-800-806-4173
Or contact us using the form below