I used `gamemode` because it seemed like a nice performance tool; however it caused performance, stability, and issues (in TeamF2). In TF2, I had irregular frame rates and frame times.
I decided to disable `gamemode` to see what would happen; because it's a good idea to test *every* known factor. **I got a consistent frame rate of 60fps and consistent frametime of 16.67ms.**
> **GameMode** is a daemon/lib combo for Linux that allows games to request a set of optimisations be temporarily applied to the host OS and/or a game process.
> GameMode was designed primarily as a stop-gap solution to problems with the Intel and AMD CPU powersave or ondemand governors, but is now host to a range of optimisation features and configurations.
> Currently GameMode includes support for optimisations including:
>* CPU governor
>* I/O priority
>* Process niceness
>* Kernel scheduler (`SCHED_ISO`)
>* Screensaver inhibiting
>* GPU performance mode (NVIDIA and AMD),
>* GPU overclocking (NVIDIA)
>* Custom scripts
Constantly changing the behavior of the CPU and priorities can be *very* bad for stability.
I think games should focus on optimizing *their code*, instead of relying on third party software.
Game boosters are known to be snake oil; FOSS game boosters are not an exception.
My mom has a business and mostly uses Windows and Mac OS X; I mentioned Linux because it could help save money.
She is unfamiliar with Linux though; I gave her some basic introduction (uncertain if it's any good, but sure), but I would like to be able to ease her into Linux *if she prefers it*.