Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

limit rate of application screen updates #4470

Closed
totaam opened this issue Jan 11, 2025 · 2 comments
Closed

limit rate of application screen updates #4470

totaam opened this issue Jan 11, 2025 · 2 comments
Labels
display enhancement New feature or request X11

Comments

@totaam
Copy link
Collaborator

totaam commented Jan 11, 2025

We already have a way of capping the virtual monitor refresh rate and screen update refresh rate: #3735
BTW, some people really do want 60fps with NVENC: #3518

Chrome is a major GPU hog and will consume tons of CPU when running in software rendering mode - which is most cases without vgl.
Does it honour the refresh rate we specify in the virtual monitor's randr data?
See show fps counter in Chrome.
Can this tool show us anything useful: fpscount

There are settings for removing the refresh rate limit: archlinux: Chromium stuckat 60fps but seemingly no way to artificially cap to a chosen limit: enable a frame rate limit in flags?
Same for Edge: Add a setting for maximum FPS limit.

Are there any other ways we can limit the application frame rate?
Something similar to vglrun -fps <f> is probably too late in the rendering as this would not affect the application's rendering frame rate.

@totaam totaam added enhancement New feature or request display X11 labels Jan 11, 2025
@totaam
Copy link
Collaborator Author

totaam commented Jan 11, 2025

FWIW: this seems to work, fpscount shows 20 when I run my server with --refresh-rate=10-20.
It drops a little lower when chromium-browser is running:
image

Chromium itself is honouring it, though it also shows a lower value than expected:
Screenshot From 2025-01-11 18-55-48

@totaam
Copy link
Collaborator Author

totaam commented Jan 11, 2025

Running chromium-browser via vglrun does reach the desired 20fps:
image

Which means that chromium's framerate is limited by the slow rendering due to the lack of GPU.
And this is also very noticeable in CPU usage.
The proper way of dealing with this problem is to use GPU acceleration with chrome (see also #4471)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
display enhancement New feature or request X11
Projects
None yet
Development

No branches or pull requests

1 participant