https://bugs.winehq.org/show_bug.cgi?id=57442
--- Comment #7 from ksmnvsg@gmail.com --- (In reply to Rémi Bernon from comment #6) I see, that makes sense. I'm working on a project that requires a very low input latency and potentially a very high response speed, so I'm trying my best to optimize whatever I can optimize, but it's hard to measure potential drawbacks like CPU usage. I can't control the applications (for my testing I just mimicked a potential application), so my only options are either redesigning Wine to use interruption instead of polling, or reduce the number of IPCs, right?
Could you also please explain how input is rerouted from application to wineserver, and then back to the application? I didn't really understand why or how, and to be fair I don't really understand what wineserver does to begin with.