Xpra: Ticket #225: calculate batch delay is expensive and hurts performance

Using profiling during #224, I found that we call calculate_batch_delay far too often and that it is way too expensive. (see callgraph attached) We now avoid calling it when we are pretty sure it won't help, see r2291:

self._damage(window, 0, 0, w, h, options={"calculate" : False, "min_delay" : 50})

What we still need to do:

Fri, 21 Dec 2012 04:23:48 GMT - Antoine Martin: attachment set

shows where the time is being spent when dealing with damage requests in UI thread

Fri, 21 Dec 2012 04:25:15 GMT - Antoine Martin: status, description changed

Tue, 08 Jan 2013 15:12:47 GMT - Antoine Martin: status changed; resolution set

This is now mostly solved, although there may be further optimizations we can make.

Sat, 23 Jan 2021 04:48:55 GMT - migration script:

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