| 6 | |
| 7 | Another thing that is worth recording is the profiling of the window updates processing (just in case there is a bottleneck I haven't seen), run the server via {{{pycallgraph}}}: |
| 8 | {{{ |
| 9 | ./tests/scripts/pycallgraph -i damage -- start :10 --start-child=xterm |
| 10 | }}} |
| 11 | and of the encoding thread: |
| 12 | {{{ |
| 13 | ./tests/scripts/pycallgraph -t encode -i '*' -e one_offs,std,libs -- start :10 --start-child=xterm |
| 14 | }}} |
| 15 | |
| 16 | I have attached an example output. |
| 17 | More info on profiling here: [/wiki/Profiling#pycallgraph]. |