tldr:
Rusty does really compete with EEVDF-BORE. The perf sched regression is the only “bigger” one, but all in all it is looking really good.
dvernet is working to fix the perf sched regression.
Rusty is also since the above commits very responsive under heavy load and rusty gets slowly to the path for a very good scheduler.
Game:
Cyberpunk 2077 v2.12
Game settings:
Preset Ultra with DLSS OFF and RT OFF
Hardware:
AMD Ryzen 7 5700X + Nvidia RTX 3060Ti + 16GB RAM 3200MHz
Kernels:
linux-cachyos-rc 6.9.rc6-4 + scx-scheds-git 0.1.9.r40.g07b521b-1
linux-cachyos-rc-lto 6.9.rc6-4
linux-cachyos-echo 6.8.9-1
linux-cachyos 6.8.9-3
amd_pstate=active mitigations=off
DE:
X11 / Wayland (once) + KDE
BIOS:
PBO and C-States disabled
Governor:
performance
Long story short - no significant differences. With each configuration I did two runs but I add only one screenshot with better result. Additionally I tested SMT ON/OFF/Auto Reflex ON/OFF and VSync ON/OFF but there was no differences in scores. Number after scheduler name is benchmark run order. Originally I planned add all screenshots.
Game:
Cyberpunk 2077 v2.12
Game settings:
Graphic settings lowest possible with DLSS Ultra Performance
Hardware:
AMD Ryzen 7 5700X + Nvidia RTX 3060Ti + 16GB RAM 3200MHz
Kernels:
linux-cachyos-rc 6.9.rc6-4 + scx-scheds-git 0.1.9.r40.g07b521b-1
linux-cachyos-rc-lto 6.9.rc6-4
linux-cachyos-echo 6.8.9-1
linux-cachyos 6.8.9-3
amd_pstate=active mitigations=off
DE:
X11 / Wayland (once) + KDE
BIOS:
PBO and C-States disabled
Governor:
performance
This time I tried to reduce GPU bottleneck. Now we have some differences so I add all screenshots. I did all benchmarks at one fell swoop so I run one more BORE extra to see how performance can be degraded when CPU is heated. Exactly order is BORE 1&2 next Rusty 1&2 next Lavd 1&2 then BORE 3. The remaining tests required restarts so heat was lower.
I was interested in how well scx_rusty handles background heavy loads so i ran some memory latency benchmarks while peazip is smashing away on 8 threads on my 5800x3d and to my pleasent surprise the latency was only slightly higher at the 262144kb page size from 56-58ns to 66-68ns very impressive.