Diagnose graphics performance issues in Remote DesktopIn this articleTo diagnose experience quality issues with your remote sessions, counters have been provided under the RemoteFX Graphics section of Performance Monitor. This article helps you pinpoint and fix graphics-related performance bottlenecks during Remote Desktop Protocol (RDP) sessions using these counters. Find your remote session nameYou'll need your remote session name to identify the graphics performance counters. Follow the instructions in this section to identify your instance of each counter.
Note While counters have RemoteFX in their names, they include remote desktop graphics in vGPU scenarios as well. Access performance countersAfter you've determined your remote session name, follow these instructions to collect the RemoteFX Graphics performance counters for your remote session.
The selected performance counters will appear on the Performance Monitor screen. Note Each active session on a host has its own instance of each performance counter. Diagnose issuesGraphics-related performance issues generally fall into four categories:
Addressing low frame rate, random stalls, and high input latencyFirst check the Output Frames/Second counter. It measures the number of frames made available to the client. If this value is less than the Input Frames/Second counter, frames are being skipped. To identify the bottleneck, use the Frames Skipped/Second counters. There are three types of Frames Skipped/Second counters:
A high value for any of the Frames Skipped/Second counters implies that the problem is related to the resource the counter tracks. For example, if the client doesn't decode and present frames at the same rate the server provides the frames, the Frames Skipped/Second (Insufficient Client Resources) counter will be high. If the Output Frames/Second counter matches the Input Frames/Second counter, yet you still notice unusual lag or stalling, Average Encoding Time may be the culprit. Encoding is a synchronous process that occurs on the server in the single-session (vGPU) scenario and on the VM in the multi-session scenario. Average Encoding Time should be under 33 ms. If Average Encoding Time is under 33 ms but you still have performance issues, there may be an issue with the app or operating system you are using. For more information about diagnosing app-related issues, see User Input Delay performance counters. Because RDP supports an Average Encoding Time of 33 ms, it supports an input frame rate up to 30 frames/second. Note that 33 ms is the maximum supported frame rate. In many cases, the frame rate experienced by the user will be lower, depending on how often a frame is provided to RDP by the source. For example, tasks like watching a video require a full input frame rate of 30 frames/second, but less computationally intensive tasks like infrequently editing a document result in a much lower value for Input Frames/Second with no degradation in the user's experience quality. Addressing poor frame qualityUse the Frame Quality counter to diagnose frame quality issues. This counter expresses the quality of the output frame as a percentage of the quality of the source frame. The quality loss may be due to RemoteFX, or it may be inherent to the graphics source. If RemoteFX caused the quality loss, the issue may be a lack of network or server resources to send higher-fidelity content. MitigationIf server resources are causing the bottleneck, try one of the following approaches to improve performance:
If network resources are causing the bottleneck, try one of the following approaches to improve network availability per session:
If client resources are causing the bottleneck, try one of the following approaches to improve performance:
Note We currently don't support the Source Frames/Second counter. For now, the Source Frames/Second counter will always display 0. Next steps
|