VMware Horizon Performance Tracker with NVidia GRID K1 Upon further investigation I noticed that my VMware BLAST sessions were not offloading h264 encoding to the video card. Symptomsīefore I was aware of this, I noticed that while 3D Acceleration and graphics were functioning, I was experiencing high CPU usage. One can assume that the agent doesn’t even attempt to check or use this function. I also checked and noticed that tools (such as nvfbcenable) were no longer bundled with the VMware Horizon agent. Ultimately after spending hours troubleshooting, I learned that NVFBC has been deprecated and is no longer support, hence why it’s no longer functioning. This function allowed the video card to capture the video frame buffer and encode it using NVENC (Nvidia Encoder). This functionality was handled via NVFBC (Nvidia Frame Buffer Capture) which was part of the Nvidia Capture SDK (formerly known as GRID SDK). This results in less CPU usage and provides a streamlined experience for the user. Originally when an environment was configured with an Nvidia GRID K1 or K2 card, not only does the card provide 3D acceleration and rendering, but it also offloads the VMware BLAST h264 stream (the visual session) so that the CPU doesn’t have to. If you’re like me and use an older Nvidia GRID K1 or K2 vGPU video card for your VDI homelab, you may notice that when using VMware Horizon that VMware Blast h264 encoding is no longer being offloaded to the GPU and is instead being encoded via the CPU.
0 kommentar(er)
