Improving performance

Game performance on Linux varies from game to game. Some games run better than on Windows, some run worse. Generally, you should be expecting about the same performance (±5%). If your experience is much worse, there is probably an issue. But even if your performance is already good, you might be able to get an even better experience, maybe even significantly better than on Windows (dependent the game, and on the hardware).

Major tweaks

This will give a huge boost for all games. If your presets are bad, this could easily double your performance:

• Install the correct drivers, especially if you have an Nvidia graphics card (GPU).
  • If you don't have an Nvidia GPU, you likely won't need to do this.
• If you use X11, disable composition.
  • X11 is the default on most Ubuntu-based beginner distros like Pop OS!
• Set GPU and CPU to maximum performance. This might not always be necessary, but will give large improvements in some cases. Definitely try it if you notice stuttering or input lag.
  • CPU: You can use GameMode or CoreCtrl to do this.
  • GPU: Read the AMD/Nvidia specific tweaks section to see how.
• Look at your thermals, and if they are too high, adapt the fan speed.

Minor tweaks

This will not make a difference as big as the major tweaks. But depending on the game, it can still give you something in the scale of ~20% FPS. Maybe more, maybe less.

• Enable Fsync. You need to use a compatible Kernel (like zen, tkg-pds, or Xanmod; kernel above 5.16 is compatible with F-sync out of the box), and enable it in Lutris: Right click the game -> Configure -> Runner options -> Enable Fsync
  • If you can't or don't want to install a kernel that is Fsync compatible, you can also enable Esync. The performance boost is usually not as large, though.
• Install an optimized kernel like zen, linux-tkg-pds, or Xanmod. This will also prevent the system from becoming unresponsive when under heavy CPU load.
  • linux-tkg-pds (linux-tkg with PDS scheduler) seems to perform better than zen, and has lower input lag (this is definitely noticeable in competitive shooters). Some people recommend using linux-tkg-bmq (linux-tkg with BMQ scheduler) to get more consistent frame times. You can get it from chaotic AUR (list of available packages). To get all benefits you have to compile it yourself, though.

Optional

• Use FSR. This might dramatically improve your framerate in GPU limited games but will definitely hurt the image quality.
• To lower your input lag even more (after doing all major and minor tweaks), you can disable page flipping (this will result in more tearing).
  • For AMD GPUs, create the following file: /etc/X11/xorg.conf.d/20-amdgpu.conf with the content:

Section "Device"
        Identifier "AMD"
        Driver "amdgpu"
        Option "TearFree" "false"
        Option "EnablePageFlip" "false"
EndSection

• Use LatencyFleX (warning: may trigger anticheat): An alternative to NVIDIA Reflex. Lowers input lag. Manually frame capping your game (so that your GPU never exceeds 80%) should be equally good. (If you use MangoHud to do this, this might add additional input lag!)
• You can use DXVK_ASYNC=1 as an environment variable to display frames even if they are not completely rendered. This will reduce stuttering a lot, but might trip anti cheat! Your wine version needs to be compatible or patched to use it. Proton-GE is compatible.
• You might want to have a look at the extensive Arch Wiki page.

Input lag, Desktop Environments, and X11/Wayland

This page needs work, for the following reason(s): Might be outdated, and there is missing data for various desktop environments and window managers.

• It appears that KDE Plasma (X11) with no composition (currently) is (one of) the best regarding performance, and input lag. Gnome is also ok.
  • Generally you should be fine if you can disable composition. This is not possible in Gnome, but Gnome uses unredirection (the same thing, Windows does) instead, which is almost as good.
• You should only use Wayland if you can enable FreeSync, because otherwise it will force vsync. If you are using KDE and you have FreeSync enabled, the performance and input lag should be close to KDE X11 with composition disabled. The input lag will increase by the "half frame" that is displayed with tearing. It's basically the question whether or not you want to wait for the frame to complete before displaying it. KDE Plasma is currently the best DE for Wayland.

It should be noted that we are talking about milliseconds here (the best value is 20ms, the worst is 90ms). If you are not susceptible to this, you may not even notice. But generally speaking, the game will feel more responsive if your input lag is low. You might also notice stuttering if your 99th percentile is bad.

AMD/Nvidia specific tweaks

AMD

• Use CoreCtrl to add performance profiles for your games, set fan speeds, and overclock/undervolt.
• Only install mesa drivers. Do not install amdgpu-pro, or amdvlk. They typically perform worse, and the system defaults to use drivers in alphabetical order (thus e.g. amdvlk being preferred over mesa).

Nvidia

This page needs work, for the following reason(s): not complete, and most is just copied from a reddit post.

• Use DKMS. DKMS is a prerequisite for using custom kernels like Zen, Xanmod or tkg with the Nvidia driver. It also lets you update to newer kernel versions without waiting for an Nvidia driver update. Every distro that has proprietary Nvidia driver support offers a DKMS version.
• The Arch Wiki is the best place to start. Enable coolbits as the link explains. Good is, setting the coolbits value to 28 on anything currently supported (post-Fermi) to enable full control over the GPU (at least, as much control as you're allowed to be given).
• Use GreenWithEnvy for overclocking, setting power limits (raise or lower) and fan curves. It's the closest alternative we have to MSI Afterburner.
• Make sure to use a Proton version of 6.3, Experimental, Proton-6.21-GE-2 or later for Proton-GE and Proton-tkg/wine-tkg-git of 6.17 or greater (or build your own) for DLSS support. For Steam, you need to put PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 %command% in your launch options (side note: there should only ever be one %command%).
• For non-Steam games, use the latest lutris or wine-ge-custom build, with Lutris, and make sure to toggle on DLSS support in the Configure -> Runner options menu. For non-Steam games, you also need a dxvk.conf file with dxgi.nvapiHack = False in it. You can just create one (mine is ~/Documents/dxvk.conf) and set DXVK_CONFIG_FILE=/path/to/dxvk.conf in your /etc/environment.
• For Arch-based distributions, use TKG's nvidia-all repo, with _dkms="" set to true in customization.cfg.

Troubleshooting

• Limiting FPS with MangoHud can introduce input lag. (I assume it adds one frame delay. It might as well be a bug, and only happen in specific scenarios. If you know more, why this happens, if, or how it can be avoided, please add information here.)
• You might have a distribution that uses PulseAudio instead of Pipewire. Pulseaudio introduces heavy audio delay. You should switch to Pipewire.