Benchmark #1195

Download
isonzo -- Rust schedulers 43

x11

Submitted 2 days ago by cuysaurus

Specifications
Label OS GPU CPU RAM OS specific
bore Steam Runtime 2 (soldier) AMD Radeon RX 6650 XT (RADV NAVI23) Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.14.0-4-cachyos performance
bore_nht Steam Runtime 2 (soldier) AMD Radeon RX 6650 XT (RADV NAVI23) Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.14.0-4-cachyos performance
bpfland Steam Runtime 2 (soldier) AMD Radeon RX 6650 XT (RADV NAVI23) Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.14.0-4-cachyos performance
bpfland_nht Steam Runtime 2 (soldier) AMD Radeon RX 6650 XT (RADV NAVI23) Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.14.0-4-cachyos performance
lavd Steam Runtime 2 (soldier) AMD Radeon RX 6650 XT (RADV NAVI23) Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.14.0-4-cachyos performance
lav_nht Steam Runtime 2 (soldier) AMD Radeon RX 6650 XT (RADV NAVI23) Intel Core i5-10600K CPU @ 4.10GHz 17 GB 6.14.0-4-cachyos performance
# Top runs: * **Highest FPS**: `bore` with a mean FPS approximately 1% higher than the others, demonstrating the best performance in terms of frames per second. * **Smoothest FPS**: `lav_nht` with the lowest standard deviation and variance in FPS, indicating the most stable and smooth performance without significant fluctuation. * **Best overall**: `lav_nht`, offering the smoothest FPS along with reasonably high average FPS, making it the most balanced choice among the runs. # Issues: * The run using `lavd` scheduler showed a significantly lower FPS mean, around 2% less than the highest, while still having a higher variance compared to `lav_nht`. This indicates worse stability without gaining FPS performance, raising potential concerns about this particular scheduler's efficiency in this testing scenario. # Summary This benchmark examined the performance of various Rust schedulers utilizing the same hardware and software configurations under Steam Runtime 2 (soldier) with a focus on stability and FPS output. The use of different schedulers, such as those depicted in the labels, offered diverse results in both frame rate stability and overall performance. While the `lav_nht` scheduler provided the smoothest experience, demonstrating the lowest variability in FPS and frame time, the `bore` scheduler achieved the highest average FPS, albeit with slightly higher instability. The findings highlight the nuanced trade-offs between maximizing frame rate and achieving frame rate consistency, offering insights into which scheduler might be optimized for specific gaming or application needs.