Hello @kattjevfel, please be aware that bleeding edge is quite literal. There is no level of quality control or support this close to active development and snafus like this will occur.
can confirm. performance on this particular proton build is abysmal.
Can you guys try to disable esync and fsync and see if that reduces the load?
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
Disabling both esync and fsync greatly lowers the CPU usage for me.
there's a futex2 / futex waitv mismatch noted at https://github.com/ValveSoftware/wine/pull/128#issuecomment-956223232. Only downstream kernels that are carrying the now obsolete futex2 patch set should be affected and PROTON_NO_FSYNC=1 should be the workaround.
https://github.com/ValveSoftware/wine/commit/a55a995020e09bfb844b12cac02351cf970287c7 in Proton Experimental 2021-11-01 should detect this scenario and disable fsync in this situation.
proton experimentalx2 2021-11PROTON_NO_FSYNC=1`x1 2021-11PROTON_NO_ESYNC=1x1 2021-11PROTON_NO_FSYNC=1x1 2021-11
As of
Proton: 1635544687 experimental-bleeding-edge-6.3-1836-20211029-paf96ce-w8a5bac-d1b1206-v430c77, as soon as Proton Experimental is launched, even when performing first time setup or even in a games launcher, it will consume all CPU withwinedevices.exebeing the worst offender. This does not happen with "normal" Proton Experimental.See screenshot below where I've launched The Witness with the previously mentioned build, its launcher should certainly not be enough to bring an AMD 3700x to its knees.
System information: https://gist.github.com/kattjevfel/9f8145327601b8449f5f1f30fdb1f53a