#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 )
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
| Milestone: | 0.9 → 1.0 |
|---|---|
| Owner: | set to Antoine Martin |
| Status: | new → accepted |
comment:2 Changed 8 years ago by
| Description: | modified (diff) |
|---|
comment:3 Changed 8 years ago by
| Status: | accepted → new |
|---|
comment:4 Changed 8 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:7 Changed 17 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/232
copyleft 2010 - 2021
Closing, I think we manage
Damagestorms well enough, the real problem withgtkperfis #505