https://bugs.winehq.org/show_bug.cgi?id=57442
--- Comment #4 from William Horvath wine@horvath.blog --- (In reply to ksmnvsg from comment #3)
I've replaced the throttling method based off ticking with the one that Wine had before 9.13 version (based off number of messages) and this latency is gone.
If I understand Rémi correctly, the commit that simplified the driver event check also had the same queuing/latency issues, it just started to present itself in a different way.
Using a higher frequency 4000hz counter (e.g. with `NtQueryPerformanceCounter`) instead of the 1000hz `NtGetTickCount` in the commit, the consistent measurements from the old impl. were restored in my test until I started sending events at >4000hz, which makes sense.
I think a small increase in the frequency like this would go a long way in accommodating quite a few applications/setups where this sort of behavior is noticeable; but in any case, it doesn't look like an easy problem to fix properly.