# Top runs: * **Highest FPS**: `BMQ GCC Run 1` with an average FPS approximately 1% above others. * **Smoothest FPS**: `BMQ GCC Run 2`, with the lowest standard deviation of FPS, indicating smoother performance. * **Best overall**: `BMQ GCC Run 1` exhibits higher FPS with slightly compromised smoothness, providing the best overall experience. # Issues: * The `BORE GCC` runs have a noticeably higher variance and standard deviation in FPS compared to others, indicating less stable performance. * Although utilizing the same GPU and similar CPU configurations, `BORE` runs exhibit higher CPU temperatures, which might affect overall system health or performance over time. * The `BORE` runs show consistently lower FPS compared to `BMQ` with approximately 1% less performance output. # Summary This benchmark compares two scheduler implementations, `BMQ` and `BORE`, over multiple runs using the same hardware configuration and focusing on FPS performance in Rocket League on a Linux system with kernel version 6.12.1. The `BMQ GCC` runs show superior performance in terms of stability and higher average FPS, establishing themselves as the top performers. Conversely, the `BORE` runs, across different compilation configurations, demonstrate a lower, more inconsistent FPS performance, highlighting potential areas for optimization or refinement in this scheduling approach to achieve a balance between smoothness and high FPS.