xpra icon
Bug tracker and wiki

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


Changes between Version 1 and Version 2 of Ticket #231


Ignore:
Timestamp:
01/08/13 06:00:40 (8 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #231 – Description

    v1 v2  
    1 We currently require all calls to {{{send()}}} to be done in the main thread, but this can be quite expensive - see this [/trac/wiki/Profiling#pycallgraph pycallgraph] diagram:
     1We currently require all calls to {{{send()}}} to be done in the main thread, but this can be quite expensive - see this [/wiki/Profiling#pycallgraph pycallgraph] diagram:
    22[[Image(https://www.xpra.org/trac/raw-attachment/ticket/231/pycallgraph-expensivetosend.png)]]
    33
     
    88
    99Most of the time used in the UI thread is to do with this network stuff, all the other things (decoding, I/O are already in separate threads and therefore do not affect latency much).
     10
     11Potential solutions:
     12* relax the threading check to ensure that the network code works when called from any thread
     13* move network code to its own thread/event based
     14* ???