https://bugs.winehq.org/show_bug.cgi?id=51420
--- Comment #11 from Henri Verbeet hverbeet@gmail.com --- (In reply to Kurt Kartaltepe from comment #10)
Perhaps unsurprisingly, removing the broken drivers xrandr 1.0 fallback that logs the now famous `Broken NVIDIA RandR detected, falling back to RandR 1.0` also works to resolve all performance issues.
The issue is probably that RandR 1.0 doesn't have RRGetScreenResourcesCurrent(), so querying the current screen configuration ends up actually polling the hardware.