GameMode 1.5 is available, Linux game performance optimizer

Feral Interactive ΠΎΠΏΡƒΠ±Π»ΠΈΠΊΠΎΠ²Π°Π»Π° optimizer release Game Mode 1.5, implemented as a background process that changes various Linux system settings on the fly to achieve maximum performance for gaming applications. The project code is written in C language and supplied under the BSD license.

For games, it is proposed to use the special libgamemode library, which allows you to request the inclusion of certain optimizations that are not used by default in the system during the execution of the game. A library option is also available to run the game in automatic optimization mode (loading libgamemodeauto.so via LD_PRELOAD when starting the game), without the need to make changes to the game code. The inclusion of certain optimizations can be controlled through the configuration file.

For example, using GameMode, power saving modes can be turned off, resource allocation and task scheduling parameters (CPU governor and SCHED_ISO) can be changed, input / output priorities can be rearranged, screen saver startup is blocked, various enhanced performance modes are enabled in NVIDIA and AMD GPUs, and NVIDIA GPUs are overclocked. (overclocking), run scripts with user-defined optimizations.

In release 1.5 added opportunity dynamic change of the CPU mode governor (CPU governor) for Intel processors with an integrated GPU, if the use of the "performance" mode leads to a drop in the performance of the graphics subsystem under high load on the GPU. In this case, switching to "powersave" mode allows you to reduce CPU power consumption and free up more GPU resources (CPU and GPU are provided with a joint power budget and priority allocation of CPU resources leads to a reduction in GPU frequency). On the CPU i7-1065G7, the proposed optimization allows you to increase the performance of the game Shadow of the Tomb Raider by 25-30%.

GameMode 1.5 also introduces a new set of D-Bus APIs using the 'pidfd' mechanism to handle the PID reuse situation (pidfd is bound to a specific process and does not change, while a PID can be bound to another process after the current process terminates, associated with this PID).

Source: opennet.ru

Add a comment