# Top runs: * **Highest FPS**: `BORE` with approximately 6% higher average FPS compared to other runs. This suggests it handles the Rocket League benchmark most efficiently in terms of frame rate. * **Smoothest FPS**: `Bpfland-next --lowlatency` with the lowest standard deviation and variance in FPS, indicating the most consistent and stable frame rate. * **Best overall**: `BORE` provides the best overall performance with not only the highest average FPS but also with a reasonable frame rate stability, making it the preferred choice for this benchmark. # Issues: * The performance of "Bpfland-main" and "Bpfland-next" configurations were around 6% lower in average FPS compared to the highest performing run "BORE." These runs also presented slightly higher frame time variance. * The "Bpfland-next -c 0 --lowlatency" run showed 6% lower average FPS with only marginal gains in consistency, suggesting a compromise might have been made for lower latency that did not result in significant FPS gains. * "Bpfland-next --lowlatency" configuration, though smoother, had an around 6% lower overall FPS when compared to the top performer "BORE." # Summary The benchmark compared multiple configurations using the `bpfland` scheduler in Rocket League on a consistent hardware setup. The `BORE` scheduler configuration on `CachyOS` under the `performance` Linux scheduler emerged as the top performer with the highest average FPS, making it the best overall choice. Various `bpfland` configurations, despite offering smoother frame rates, lagged by around 6% in FPS performance, indicating that the `BORE` scheduler might be better optimized for this particular workload in Rocket League.