Best desktop frame full#
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. 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. Note that 33 ms is the maximum supported frame rate.
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. Frames Skipped/Second (Insufficient Client Resources)Ī high value for any of the Frames Skipped/Second counters implies that the problem is related to the resource the counter tracks.
Frames Skipped/Second (Insufficient Network Resources).Frames Skipped/Second (Insufficient Server Resources).There are three types of Frames Skipped/Second counters: To identify the bottleneck, use the Frames Skipped/Second counters. If this value is less than the Input Frames/Second counter, frames are being skipped. It measures the number of frames made available to the client. Graphics-related performance issues generally fall into four categories:Īddressing low frame rate, random stalls, and high input latencyįirst check the Output Frames/Second counter. Your counter instances include the VM name instead of the number in the session name, such as "Win8 Enterprise VM."Įach active session on a host has its own instance of each performance counter. If your session is hosted in a VM that supports virtual Graphics Processing Units (vGPU): Your instance of each counter is stored on the server instead of in your VM.If your session is hosted in a multi-session virtual machine (VM): Your instance of each counter is suffixed by the same number that suffixes your session name, such as "rdp-tcp 37.".Run the qwinsta command and find your session name.