xpra icon
Bug tracker and wiki

Changes between Version 1 and Version 2 of Ticket #797, comment 7


Ignore:
Timestamp:
06/16/15 17:19:49 (4 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #797, comment 7

    v1 v2  
    44* vpx is now very competitive with h264 (#832), we use more threads - use more cpu, encode faster at a higher quality setting, and send more pixels
    55* disappointing pixels/s figures: we seem to have lost a few percent there - and this is one of the most important metrics..
    6 * x264 looks to have regressed with glxgears / glxspheres (batch delay through the roof)
     6* x264 seems to have regressed with glxgears / glxspheres (batch delay through the roof)
    77* batch delay is way too high in the latest v0.15.x (is the revision shown anywhere? please show it somewhere) - it looks like less than 4 fps! Worst case (max batch delay) is just 1 fps!! Quite strange seeing that the number of pixels and regions sent is more or less unchanged.
    88* mmap has also regressed
     
    1212* please show the client rss
    1313
    14 Executive summary: we have serious quality control issues. We should have tackled those regressions during the 0.15 development cycle, not half way through the 0.16 release cycle.
     14Executive summary: we have serious quality control issues. We should have tackled those regressions during the 0.14 or 0.15 development cycles, not half way through the 0.16 release cycle.
    1515This data should be collected daily or weekly so we can identify regressions. And now this will need to be done anyway to identify the source of the regressions, more than doubling up the amount of work required to fix them.