Xpra: Ticket #543: allow the client more control over window update speed

The client may offer an enhanced UI to let the user select which windows are more important (ie: #539), or we can detect which windows are more important: if a window is not shown on the current desktop, we don't need to refresh it at full speed!

Thu, 20 Mar 2014 11:29:32 GMT - Antoine Martin: attachment set

when the window is not on the current workspace, limit its update speed

Thu, 20 Mar 2014 11:31:59 GMT - Antoine Martin: owner, status changed

The patch above is in pretty good shape, it overloads the "buffer-refresh" packet with the ability to:

The window refresh drops dramatically when it isn't on the current desktop (though still higher than I expected - to investigate)

Thu, 20 Mar 2014 14:11:20 GMT - Antoine Martin: attachment set

before moving the window to another workspace on the left, after on the right

Thu, 20 Mar 2014 14:13:39 GMT - Antoine Martin:

Merged in r5870, it works really well.

Here's the most extreme example, using the speed setting "low latency" with x264: before moving the window to another workspace on the left, after on the right

With more reasonable settings, the bandwidth savings are still impressive, usually about 8 times less once the throttling kicks in.

I am keeping the ticket open for further testing, and probably refactor the code a little to use it on suspend / resume (see #492)

Fri, 21 Mar 2014 04:32:24 GMT - Antoine Martin: status changed; resolution set

Hooked into the power events callbacks in r5875 - see #492.

Will probably do more on this as part of #540.

Sat, 23 Jan 2021 04:58:52 GMT - migration script:

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