Anyway, I think that 20% CPU for movie decoding sort of gives away the approximate computing power of the VM, give or take. The CPU profile of the VM is a 2-socket setup, each CPU with 1 core. The VM is set up with a vGPU that is backed by Nvidia GRID K1 card, profile K120Q (the bottom baseline). What seems to matter is the amount of screen area being updated, affecting the H.264 encoding of the screen framebuffer. The Windows Media Player itself does not use more than 20% of the virtual CPU, so I don't think that the codec etc really matter here. The scenario is Windows Media Player playing a movie (Big Buck Bunny 720p, AVI) which occupies 1/3 of the screen area. So this is an anomaly, but I am not sure where to approach it. I have to admit that we have several VMs beside the one I am having trouble with, and I recall we've had a number of well behaving installations where the protocol process on a VM did not account for more than 5% CPU usage in similar scenarios. I am connected on a LAN with the Horizon Client. I have abnormally high CPU usage for what I assume is the process responsible for H.264 screen encoding - `VMBlastW.exe`.
0 kommentar(er)
