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.įor more information about diagnosing app-related issues, see User Input Delay performance counters.īecause RDP supports an Average Encoding Time of 33 ms, it supports an input frame rate up to 30 frames/second. Average Encoding Time should be under 33 ms. 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. 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. 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.
Open the Windows command prompt from your remote session.
Follow the instructions in this section to identify your instance of each counter. You'll need your remote session name to identify the graphics performance counters. This article helps you pinpoint and fix graphics-related performance bottlenecks during Remote Desktop Protocol (RDP) sessions using these counters.
To diagnose experience quality issues with your remote sessions, counters have been provided under the RemoteFX Graphics section of Performance Monitor.