xpra icon
Bug tracker and wiki

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


Ignore:
Timestamp:
11/26/17 12:19:21 (22 months ago)
Author:
Antoine Martin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #999, comment 23

    v1 v2  
    33I think this is as good as it is going to get for this release. We can improve it some more in #1700.
    44
    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.
     5
     6----
     7
     8
     9@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 - this works better if we know in advance that there are limits (#417).
    610It's a balancing act between quality, bandwidth usage and framerate.
    711
     
    913
    1014When 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.
     15
     16
     17----
     18
     19Some links for testing bandwidth constraints:
     20* [https://www.netlimiter.com/ netlimiter] (win32) is quite easy to use, not sure how well it simulates network congestion
     21* [https://serverfault.com/questions/507658/ Limit incoming and outgoing bandwidth and latency in linux]
     22* [http://mark.koli.ch/slowdown-throttle-bandwidth-linux-network-interface Manually Throttle the Bandwidth of a Linux Network Interface]
     23* [https://serverfault.com/questions/787006/ How to add latency and bandwidth-limit interface using tc?]
     24* [https://wiki.archlinux.org/index.php/advanced_traffic_control Advanced traffic control]