Benchmark #244

Download
Isonzo -- Rust schedulers 9

Submitted 1 month ago by cuysaurus

Specifications
Label OS GPU CPU RAM OS specific
bore CachyOS NVIDIA GeForce RTX 2060 Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.10.5-2-cachyos performance
bore2 CachyOS NVIDIA GeForce RTX 2060 Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.10.5-2-cachyos performance
bpfland CachyOS NVIDIA GeForce RTX 2060 Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.10.5-2-cachyos performance
lavd CachyOS NVIDIA GeForce RTX 2060 Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.10.5-2-cachyos performance
rusty CachyOS NVIDIA GeForce RTX 2060 Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.10.5-2-cachyos performance
# Top runs: * **Highest FPS**: `bore` with an average FPS significantly higher than other runs, offering an enhanced performance. * **Smoothest FPS**: `lavd` displaying the lowest standard deviation and variance in FPS, providing the most consistent frame rates. * **Best overall**: `bore` as it not only has the highest FPS but also maintains a relatively low variance in FPS, balancing between performance and consistency. # Issues: * The run using the `bpfland` scheduler exhibits considerably lower FPS, with an average FPS notably lower than other runs. Additionally, the FPS variance is higher, leading to inconsistent frame rates. * Another noticeable discrepancy is the use of a significantly higher swap memory in the run with `bore2` scheduler. This is atypical compared to other runs and might indicate suboptimal performance management. # Summary: This benchmark compares various Rust-based schedulers (`bore`, `bore2`, `bpfland`, `lavd`, `rusty`) on a constant hardware setup using `CachyOS` and `performance` Linux scheduler. The `bore` scheduler stands out by delivering the highest average FPS with commendable consistency, making it the best overall choice. The `lavd` scheduler excels in terms of smoothness, showing the lowest frame rate variance. However, the `bpfland` scheduler underperforms with a significantly lower average FPS and higher variance, highlighting potential stability issues. The `bore2` scheduler also shows unusual high swap usage, which might need further investigation. Overall, the `bore` scheduler appears to be the most balanced option, providing both high performance and stable frame rates.