Skip to main content

Thread: debug x11vnc performance


hi,

able data x11vnc process determine bottleneck me. need benchmark particular stages x11vnc , vnc client work - change detection display of data on client screen.

example: how screen change x11vnc seeing, compression ratio of these changes; frame size; latency between change detected , data sent on network; , more, not sure how x11vnc internally works reading material appreciated

thanks,
michal

this might started...

if run x11vnc "-forever" option, when viewer disconnects statistics printed out:
code:
19/06/2011 22:38:27 client 127.0.0.1 gone  19/06/2011 22:38:27 statistics             events    transmit/ rawequiv ( saved)  19/06/2011 22:38:27  servercuttext       :      1 |         8/        8 (  0.0%)  19/06/2011 22:38:27  framebufferupdate   :     31 |         0/        0 (  0.0%)  19/06/2011 22:38:27  lastrect            :     13 |       156/      156 (  0.0%)  19/06/2011 22:38:27  tight               :    575 |    213514/  3504756 ( 93.9%)  19/06/2011 22:38:27  pointerpos          :      1 |        12/       12 (  0.0%)  19/06/2011 22:38:27  richcursor          :      1 |       726/      726 (  0.0%)  19/06/2011 22:38:27  totals              :    622 |    214416/  3505658 ( 93.9%)  19/06/2011 22:38:27 statistics             events    received/ rawequiv ( saved)  19/06/2011 22:38:27  pointerevent        :     21 |       126/      126 (  0.0%)  19/06/2011 22:38:27  framebufferupdate   :     32 |       320/      320 (  0.0%)  19/06/2011 22:38:27  setencodings        :      1 |        64/       64 (  0.0%)  19/06/2011 22:38:27  setpixelformat      :      1 |        20/       20 (  0.0%)  19/06/2011 22:38:27  totals              :     55 |       530/      530 (  0.0%)
also, if run "-debug_tiles" option strange looking output regarding screen changes, e.g.:
code:
============================= tiles: 99  dt: 0.0508  t: 4.9359  3.99 mb/s nap_ok: 0  ============================= tiles: 8  dt: 0.0110  t: 4.9895  1.48 mb/s nap_ok: 0  ============================= tiles: 0  dt: 0.0072  t: 5.0214  0.00 mb/s nap_ok: 0  ============================= tiles: 8  dt: 0.0115  t: 5.0750  1.43 mb/s nap_ok: 0
the main thing remember x11vnc "tile" 32x32 pixel patch on screen. "tiles: 99" means 99 changed tiles detected , read in screen.

if supply option twice more output, including when there no screen changes... might big mess.

there may more profiling things inside x11vnc that's can remember. possible turn on xdamage debug output , if willing recompile turn on ascii print out of locations of changed tiles (ask if interested in either one)

please framebuffer read rate reported be. e.g.:
code:
19/06/2011 23:54:26 fb read rate: 9 mb/sec
a low framebuffer read rate (like above) can make things laggy because takes long read changed pixel regions in screen (the video ram)


Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [ubuntu] debug x11vnc performance


Ubuntu

Comments