xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Changes between Initial Version and Version 1 of Ticket #443


Ignore:
Timestamp:
10/16/13 06:53:57 (8 years ago)
Author:
Antoine Martin
Comment:

Please confirm that those steps work.

As of r4506 you should be able to see when the lz4 compression is enabled client side via session info: /raw-attachment/ticket/443/session-info-lz4-win32.png

And as of r4507 via "xpra info" too:

$ xpra info | grep connection.compression=
client.connection.compression=lz4

Notes:

  • lz4 is enabled by default when compression level is set to 1 and both sides support it.
  • you can verify that the current client supports lz4 with:
    xpra info | grep client.features.lz4
    
  • with r4885 onwards, you can verify that the server supports it with:
    xpra info | grep network.lz4
    
  • with r4895 and the new xpra control feature (see #461), one can also change the encoder and compressor at runtime, ie:
    xpra control :10 compression lz4
    
    If lz4 is not present, this will return an error (beware this change takes effect whether the client supports lz4 or not..)
  • with r4889, you can also see which packet encoders and compressors are available for both client and server:

/raw-attachment/ticket/443/show-packet-encoders-and-compressors.png

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #443

    • Property Owner changed from Antoine Martin to Smo
  • Ticket #443 – Description

    initial v1  
    1 This ticket is just for reference, here's how one adds lz4 compression to the win32 builds (more info on packet encoding and compression [/wiki/PacketEncoding here] - lz4 is '''fast!''') since simply doing an {{{scripts\easy_install -Z lz4}}} sadly fails:
     1This ticket is just for reference, here's how one adds {{{lz4}}} compression to the win32 builds (more info on packet encoding and compression [/wiki/PacketEncoding here] - lz4 is '''fast''' !) since simply doing an {{{scripts\easy_install -Z lz4}}} sadly fails because of ggc-isms in the build files:
    22* download [https://pypi.python.org/pypi/lz4 lz4]
    33* uncompress the archive
     
    1111C:\Python\Python.exe setup.cfg install
    1212}}}
     13(see below for fixing the {{{-mno-cygwin}}} error)
     14* unzip the egg which has been installed (usually found in "{{{C:\Python27\Lib\site-packages\lz4*.egg}}}") so py2exe packaging will find it
     15* build the installer with py2exe
     16
     17
     18----
    1319
    1420If you get an "{{{Unrecognized command line option '-mno-cygwin'}}}" compilation error, simply remove all the references to {{{'-mno-cygwin'}}} from "{{{cygwinccompiler.py}}} (usually located in {{{C:\Python27\Lib\distutils\cygwinccompiler.py}}}) - as per this answer: [http://stackoverflow.com/questions/6034390/compiling-with-cython-and-mingw-produces-gcc-error-unrecognized-command-line-o Compiling with cython and mingw produces gcc: error: unrecognized command line option '-mno-cygwin']