Since we (human beings) can’t tell the difference between 60 and 300 FPS (at least I haven’t met anybody yet that can), wouldn’t it be better to limit the FPS of the first user to 60 and let the second user leverage the now available GPU cycles to increase his user experience to higher than 10 FPS?įrame Rate Limiter does exactly that, it will allow the 3D Engine to render 60 FPS for the first user while the second user benefits from the now available GPU cycles to increase his user experience. The first user is running a lightweight application at 300 FPS whereas the second users is running a heavy application at 10 FPS. Imagine the following scenario (Frame Rate Limiter turned off) where two users are working on the same physical GPU (vGPU accelerated VDI VMs). Frame Rate Limiter helps saving resources which then can be leveraged by additional users to increase scalability.įrame Rate Limiter limits the 3D Engine to not render more than 45/60 FPS to save and balance GPU cycles of the 3D Engine between vGPUs. One of many ways to make a VDI/RDSH solution more interesting to customers is to increase scalability and therefore decrease the cost per user. How can the Frame Rate Limiter increase user experience? Frame Rate Limiter is set to 45 FPS for the vApps and vPC software editions (These are the “A” and “B” profiles) and set to 60 FPS for the vWorkstation software edition (This is the Quadro “Q” profiles). The Frame Rate Limiter is turned on by default and will limit the 3D Engine to not render more than 45 or 60 Frames per Second (FPS) for each vGPU. The Frame Rate Limiter (FRL) is the primary mechanism to balance the performance across multiple vGPUs executing on the same physical GPU. Let’s have a closer look into why NVIDIA GRID has a Frame Rate Limiter (FRL) and what it is set to in the various software editions.
0 Comments
Leave a Reply. |