Benchmark #1590

Download
BORE in Rocket League | kernel compilation

First minute of match replay | Kernel compilation in background

Submitted 2 weeks ago by yubysowhat

Specifications
Label OS GPU CPU RAM OS specific
BORE 5.9.6 Steam Runtime 3 (sniper) NVIDIA GeForce RTX 3060 Ti AMD Ryzen 7 5700X 8-Core Processor 34 GB 6.16.0-rc5-1596 powersave
BORE 6.0.0-beta5 Steam Runtime 3 (sniper) NVIDIA GeForce RTX 3060 Ti AMD Ryzen 7 5700X 8-Core Processor 34 GB 6.16.0-rc5-1600b5 performance
EEVDF Steam Runtime 3 (sniper) NVIDIA GeForce RTX 3060 Ti AMD Ryzen 7 5700X 8-Core Processor 34 GB 6.16.0-rc5-1EEVDF performance
# Top runs: * **Highest FPS**: `BORE 6.0.0-beta5` with the highest average FPS, outperforming the other runs by a noticeable margin. * **Smoothest FPS**: `EEVDF` with the lowest standard deviation and variance, indicating more consistent frame times compared to other runs. * **Best overall**: `BORE 6.0.0-beta5`, as it achieves significantly higher FPS with an acceptable level of FPS variation, balancing performance and smoothness effectively. # Issues: * The configuration using the `EEVDF` scheduler experienced significantly lower FPS performance, approximately 34% less than competing configurations, with a noticeably higher frame time variance. This indicates potential compatibility or optimization issues within this scheduler for the given benchmark. * Hardware and operating system configurations remained consistent across all tests, indicating the issue is likely related to the scheduler being used rather than any hardware or OS discrepancies. # Summary The benchmark data compares different Linux scheduler configurations during a Rocket League game replay with a background kernel compilation on a consistent hardware and software setup. The `BORE 6.0.0-beta5` configuration using the `performance` scheduler delivered the highest FPS, significantly enhancing the gaming experience over the other tested configurations. Despite the potential of `EEVDF`, its substantially lower FPS suggests less optimization or compatibility in such a dual-load scenario. Overall, the data suggests that leveraging the `performance` scheduler under the tested conditions offers the best balance between smoothness and peak performance.