# Top runs: * **Highest FPS**: `BORE-5-2-4-mediumload-youtube1080p30-discordcall` with a mean FPS significantly higher than other runs, surpassing `LAVD-mediumload-youtube1080p-discordcall` by a small percentage. * **Smoothest FPS**: `BPFLAND-next-5ms-mediumload-youtube1080p30-discordcall` with the lowest standard deviation and variance in FPS, indicating a more consistent performance. * **Best overall**: `BORE-5-2-4-mediumload-youtube1080p30-discordcall` due to its high average FPS and good consistency, making it the best balance between high performance and stability. # Issues: * The run using `BPFLAND-next-5ms-highload-discordcall-kernelcomp-youtube1080p30` shows a significant drop in FPS compared to other high-load runs, which is backed by a notably lower mean FPS. * `BPFLAND-next-20ms-highload-kernelcomp-discordcall-youtube1080p30` also underperforms, showing one of the lowest mean FPS among high-load runs, indicating the scheduler is less efficient under extreme stress. * `RUSTY-highload-discordcall-kernelcomp-youtube1080p30` presents noticeably higher FPS variability, with a high standard deviation indicating inconsistent performance during high-load conditions. # Summary The benchmark comparing different Linux schedulers under varying system load while running Overwatch 2 stress tests shows how each scheduler handles multitasking stress. The `BORE-5-2-4` configuration consistently delivers the highest FPS under medium loads, offering both performance and stability. In contrast, the `BPFLAND-next-5ms` scheduler provides the smoothest FPS in medium-load scenarios. However, both `BPFLAND-next-5ms` and `BPFLAND-next-20ms` significantly underperform under high load, indicating their inefficiency in more demanding environments. The benchmark highlights how the choice of scheduler can impact gaming performance, especially under different system loads.