Linux is difficult to call a gaming system for a number of reasons. Firstly, modern graphical interfaces are not always supported on a free OS, and drivers work "halfway". Secondly, many games are simply not ported, although Wine and other solutions partially fix this.
However, the Google Stadia project was supposed to solve such problems. But this is only in theory. In fact, the developers of "cloud" games when porting them to Linux with problems that concern, among other things, the kernel scheduler of the system.
Developer Malte Skarupke reported that the Linux kernel scheduler is bad, although patches like MuQSS are partially improving the situation. However, in general, this part of the OS is far from ideal. And MuQSS itself has its own problems. At the same time, as it turned out, a similar solution in Windows works much better.
The bottom line is that for Google Stadia, the refresh rate of the image on the screen is very important. After all, games, in fact, are executed on remote servers, and users only receive a picture. Therefore, along with a good bandwidth of the Internet channel, the speed of the software is also important. But with this just problems.
Such shortcomings were revealed during the porting of the action movie Rage 2 to Stadia. Considering that the system supports a frame refresh rate of 30 or 60 FPS, each frame is rendered in 33 or 16 ms, respectively. If the rendering time is longer, then the game will simply slow down, and on the client side.
The developers claim that this problem is not only in Rage 2, but Google is aware of the situation and is working on a fix, although no one has yet given specific dates.
MuQSS showed the best results for this, so it is expected that sooner or later it will be added to the kernel to replace the current scheduler. It remains to be hoped that this will happen this year.
Source: 3dnews.ru