locked
Compression Algorithm RRS feed

  • Question

  • I saw this on the App-V Blog related to sequencing operations:

    http://blogs.technet.com/softgrid/archive/2007/08/24/inside-the-sequencer-part-2.aspx
    Compression Algorithm: Allows the Sequence Engineer to compress or not compress the SFT file. If you chose to compress the SFT file it will be smaller and stream faster over the network, but will take longer for the application’s initial launch on the SoftGrid Client. This is because the decompression algorithm is CPU intensive. The default setting is “No Compression” and should be left unless the target LAN for streaming is excessively slow.

    Is this saying that you pay a penalty EACH time the application is launched on the client or is the application uncompressed when it is stored within the cache?  A one time penalty for the gains in compression doesn't seem too bad, but if this uncompression happens EACH time the application is launched that would seem to make a bigger difference.
    Thursday, January 28, 2010 4:45 PM

Answers

  • Hello,

    THe uncompression should happen at the time its loaded into the cache, not at every execution time.

    /Znack
    • Proposed as answer by kirk_tnModerator Thursday, January 28, 2010 9:09 PM
    • Marked as answer by Redparadox Friday, January 29, 2010 12:27 PM
    Thursday, January 28, 2010 4:46 PM

All replies

  • Hello,

    THe uncompression should happen at the time its loaded into the cache, not at every execution time.

    /Znack
    • Proposed as answer by kirk_tnModerator Thursday, January 28, 2010 9:09 PM
    • Marked as answer by Redparadox Friday, January 29, 2010 12:27 PM
    Thursday, January 28, 2010 4:46 PM
  • Best practice, in my opinion is to compress, and fill the cache.  You get he bennefit and the user does not suffer any delay -- not that it is much of one.  If a modern CPU can't compress faster than the streaming you have a dog of a PC!
    Thursday, January 28, 2010 11:04 PM
    Moderator