A: Once RemoteFX is enabled on a Hyper-V server, there are three groups of performance counters available:
- RemoteFX Root GPU Management: Gives information for the GPU in the Hyper-V host as it relates to RemoteFX.
- RemoteFX Software: Gives counters specific to each RemoteFX-enabled virtual machine (VM).
- RemoteFX VM vGPU Management: Gives information for each GPU as it relates to each RemoteFX-enabled VM. In this case, TDR means Timeout Detection and Recovery. It helps detect when the GPU stops responding then tries to fix it via a re-initialization, avoiding the need for reboots.
As shown below, when sessions aren't connected to a RemoteFX-enabled VM, the only counters to show information are the RemoteFX Root GPU Management. If the VM isn't running, VMs running RemoteFX shows 0. Here you can see the percentage of GPU memory this VM has allocated and the amount remaining.
Once I create a session to the VM and run something graphically intensive (Halo 2), you can see that the other counters now show actual performance data, including the capture rate, compression ratio, response time, and output data. You can see I have no delays in my current environment because the delayed frames/sec and waiting for client count/sec are 0.
On the RemoteFX enabled VM, there are also additional counters under the "RemoteFX VM vGPU Performance" group to give information directly from the client.