Benchmark #92

Download
Overwatch 2 Stress test map (EXTREME), Schedulers comparision - No background load, only game

Submitted 1 month ago by aarrayy

Specifications
Label OS GPU CPU RAM OS specific
BORE-nobackgroundload Steam Runtime 3 (sniper) AMD Radeon R7 370 Series (RADV PITCAIRN) AMD FX-6300 Six-Core Processor 12 GB 6.10.0-1-cachyos
BPFLAND-1ms-nobackgroundload Steam Runtime 3 (sniper) AMD Radeon R7 370 Series (RADV PITCAIRN) AMD FX-6300 Six-Core Processor 12 GB 6.10.0-1-cachyos
BPFLAND-5ms-nobackgroundload Steam Runtime 3 (sniper) AMD Radeon R7 370 Series (RADV PITCAIRN) AMD FX-6300 Six-Core Processor 12 GB 6.10.0-1-cachyos
BPFLAND-20ms-nobackgroundload Steam Runtime 3 (sniper) AMD Radeon R7 370 Series (RADV PITCAIRN) AMD FX-6300 Six-Core Processor 12 GB 6.10.0-1-cachyos
LAVD-nobackgroundload Steam Runtime 3 (sniper) AMD Radeon R7 370 Series (RADV PITCAIRN) AMD FX-6300 Six-Core Processor 12 GB 6.10.0-1-cachyos
RUSTY2-nobackgroundload Steam Runtime 3 (sniper) AMD Radeon R7 370 Series (RADV PITCAIRN) AMD FX-6300 Six-Core Processor 12 GB 6.10.0-1-cachyos
### Top runs - **Highest FPS**: `BPFLAND-5ms-nobackgroundload` achieved the highest average FPS with values approximately 6% higher than the next best run. - **Smoothest FPS**: `LAVD-nobackgroundload` had the lowest FPS variance, showing about 50% more stability than the most unstable run. - **Best overall**: `BPFLAND-5ms-nobackgroundload` provides the best performance overall, balancing high FPS and decent stability. ### Issues - **BORE-nobackgroundload**: This run had significantly lower FPS, almost 7% lower on average compared to the highest FPS run and around 5% less stable than the most stable run. ### Summary This benchmark of Overwatch 2 stress test map on different Linux schedulers without background load provided insights into 6 runs. All runs used identical hardware and software configurations to ensure consistency. `BPFLAND-5ms-nobackgroundload` demonstrated the highest FPS, performing roughly 6% better compared to its peers, while `LAVD-nobackgroundload` showed the smoothest performance in terms of FPS stability, being 50% more stable than the least stable run. However, `BORE-nobackgroundload` exhibited notably lower performance, around 7% lower FPS on average, which could indicate issues with either the scheduler or other unseen variances. The majority of other runs performed similarly with minor variances, balancing between frame rate and stability.