xpra icon
Bug tracker and wiki

Changes between Initial Version and Version 1 of Ticket #999, comment 23


Ignore:
Timestamp:
11/26/17 12:09:21 (3 years ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #999, comment 23

    initial v1  
    22
    33I think this is as good as it is going to get for this release. We can improve it some more in #1700.
    4 Bear in mind that a lossless refresh will use up a few seconds' worth of bandwidth, this is unavoidable. We try to avoid doing that if we can.
     4
     5@maxmylyn: bear in mind that a lossless refresh will use up a few seconds' worth of bandwidth, this is unavoidable. We try to delay the refresh as much as possible, especially when we know the bandwidth is limited.
    56It's a balancing act between quality, bandwidth usage and framerate.
    67
    7 When debugging, we want to see: "-d refresh,compress,regionrefresh", and the usual "xpra info".
     8We need results from the automated tests to ensure that the performance has not regressed for the non-bandwidth-constrained case.
     9
     10When debugging, we need: "-d refresh,compress,regionrefresh", and the usual "xpra info". And a reproducible test case that does not involve user interaction, as I've launched glxspheres literally thousands of times to get here.