MWO scheduler test #2

2 months ago

scx-scheds-git 1.0.2.r129.g0394469-1. All graphics very high, no AA. Still CPU limited. No user.cfg. All runs using PROTON_USE_WINESYNC=1 for the notable uplift in this game. taskset -c 0-5,12-17 used for those runs. MWO seems to suffer when cache has to move between CCDs? Game was restarted for each scheduler, and the run used is a second go due to a consistent stutter on an early turn in the first. 95 second run through Solaris City in a Huntsman.

By thisusernamechangethingisdumb

MWO scheduler test

3 months ago

Didn't switch to max settings, but most are high. MWO is incredibly CPU reliant either way. 100s run through Solaris City. 100 log interval. taskset=taskset -c 0-5,12-17 for the first CCD.

By thisusernamechangethingisdumb