xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Opened 9 years ago

Closed 8 years ago

Last modified 17 months ago

#232 closed task (wontfix)

deal with damage request storms

Reported by: Antoine Martin Owned by: Antoine Martin
Priority: major Milestone: 2.0
Component: server Version: trunk
Keywords: Cc:

Description (last modified by Antoine Martin)

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?

Change History (7)

comment:1 Changed 9 years ago by Antoine Martin

Milestone: 0.91.0
Owner: set to Antoine Martin
Status: newaccepted

comment:2 Changed 8 years ago by Antoine Martin

Description: modified (diff)

comment:3 Changed 8 years ago by Antoine Martin

Status: acceptednew

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

comment:4 Changed 8 years ago by Antoine Martin

Resolution: wontfix
Status: newclosed

comment:5 Changed 6 years ago by Antoine Martin

Milestone: 1.01.1

Milestone renamed

comment:6 Changed 6 years ago by Antoine Martin

Milestone: 1.12.0

Milestone renamed

comment:7 Changed 17 months ago by migration script

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

Note: See TracTickets for help on using tickets.