Benchmark #1122

Download
osu!stable + stress-ng - lavd vs bpfland vs flash-next

Submitted 4 days ago by .dnaim

Specifications
Label OS GPU CPU RAM OS specific
lavd-no-futex Steam Runtime 3 (sniper) AMD Radeon Graphics AMD Ryzen 5 6600HS Creator Edition 14 GB 6.14.0-rc5-1-cachyos-rc powersave
lavd Steam Runtime 3 (sniper) AMD Radeon Graphics AMD Ryzen 5 6600HS Creator Edition 14 GB 6.14.0-rc5-1-cachyos-rc powersave
flash-5ms Steam Runtime 3 (sniper) AMD Radeon Graphics AMD Ryzen 5 6600HS Creator Edition 14 GB 6.14.0-rc5-1-cachyos-rc powersave
flash Steam Runtime 3 (sniper) AMD Radeon Graphics AMD Ryzen 5 6600HS Creator Edition 14 GB 6.14.0-rc5-1-cachyos-rc powersave
bpfland Steam Runtime 3 (sniper) AMD Radeon Graphics AMD Ryzen 5 6600HS Creator Edition 14 GB 6.14.0-rc5-1-cachyos-rc powersave
# Top runs: * **Highest FPS**: `lavd` with approximately 6% higher average FPS than the next best run. * **Smoothest FPS**: `lavd` with the lowest standard deviation, offering approximately 10% less variability compared to the next smoothest run. * **Best overall**: `lavd` due to its high FPS coupled with smooth frame render, providing a balanced combination better than others. # Issues: * Both configurations under `flash` label show approximately 28-36% lower average FPS than the best performing setup, indicating a significant performance discrepancy. * The `flash` configuration demonstrably suffers from higher frame time variance, impacting smoothness significantly more than others. # Summary This benchmark compares different scheduling configurations under the same hardware and runtime settings, where schedulers `lavd` and `bpfland` offer much higher and smoother average frames per second than the `flash` option. In particular, `lavd` excels because it maintains low frame time variance along with high average FPS, making it superior for both speed and consistency. The `flash` configuration significantly underperforms, with substantial variability in frame rendering and reduced FPS, indicating that the scheduling mechanism does not handle resource allocation as efficiently as `lavd` or `bpfland`.