Xpra: Ticket #232: deal with damage request storms

Split from #224: gtkperf can cause some severe x11 Damage storms where so many requests come in at once that our code struggles to keep up and the system latency goes through the roof.

Removing the many levels of indirection may help a little as we currently have to go from the UI event loop to CompositeHelper to WindowModel to Server to ServerSource to WindowSource(s)

But ultimately, I don't think the python code will be fast enough to deal with these storms reliably, we should therefore move the damage batching to the event loop so that we only fire the python code once we know that the damage event is likely to result in a real action rather than a lot of churn just to postpone until later. Or maybe #505 is enough to fix the problem?

Wed, 20 Mar 2013 14:23:20 GMT - Antoine Martin: status, milestone changed; owner set

Sat, 15 Feb 2014 11:43:04 GMT - Antoine Martin: description changed

Mon, 19 May 2014 12:04:04 GMT - Antoine Martin: status changed

Closing, I think we manage Damage storms well enough, the real problem with gtkperf is #505

Mon, 19 May 2014 12:04:11 GMT - Antoine Martin: status changed; resolution set

Tue, 12 Jul 2016 16:51:50 GMT - Antoine Martin: milestone changed

Milestone renamed

Sun, 21 Aug 2016 09:55:49 GMT - Antoine Martin: milestone changed

Milestone renamed

Sat, 23 Jan 2021 04:49:07 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/232