this post was submitted on 12 Dec 2023
86 points (94.8% liked)
Linux
48153 readers
1105 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Depending on what you perceive as snappiness, it is because of misconfiguration.
If you perceive response time of desktop enviroment snappiness, you need to configure desktop server(xorg-server, kwin_wayland, xwayland) and compositor(or disable it) to run in real-time mode. Maybe there is also "prefer smoothness" option in you desktop enviroment settings like on KDE.
If you play games, then migrate to X11. Games don't know how to enable tearing on wayland. And in general X11 seems to work better with games.
What do you mean with real-time mode?
I only know of real-time kernels, which allow to measure/calculate the maximum response time of an application. This is important for critical processes, like braking in your car, but decreases performance slightly rather than increase responsiveness.
I mean real-time scheduler, not real-time kernel. Found an article that says kwin_wayland uses SCHED_FIFO.
man 7 sched
says:Responsiveness is not performance. There are 3 main performance metrics: throughput, latency and jitter. Responsiveness is mostly latency, but sometimes jitter. You can for example run game in 30fps with 0.01s lag or in 60 fps with 1s lag. In second case FPS is higher, but, player will feel game unresponsive because of time it takes between pressing button and game showing the result.
Thanks for the link, real-time mode definitely makes sense and should be implemented for all compositors imo.
True, I miswrote. What I wanted to write was