https://bugs.winehq.org/show_bug.cgi?id=51420
--- Comment #42 from Kurt Kartaltepe kkartaltepe@gmail.com ---
however, if only nVidia GPU's would exhibit this kind of behaviour if this particular for sequence is used, perhaps it is a driver issue someone should consider bugreporting?
You are probably 15 years and 5 versions of randr too late to argue that nvidia's implementation is incorrect.
The issue is probably that RandR 1.0 doesn't have RRGetScreenResourcesCurrent(), so querying the current screen configuration ends up actually polling the hardware.
As you can see from a previous comment, newer versions of randr (the version used on every other driver by wine) have a new function, presumably for precisely this reason. This is also why you can issue the same xrandr function in a loop without forcing version 1.0 (no `--q1` flag) and observe there is no significant performance issues on nvidia.
Intel drivers freak out a bit with an eDP device on randr 1.0 but dont cause any significant performance impact, i dont have any other devices with to test on though, nor do I kid myself that nvidia would change their implementation of randr 1.0.