Performance Overhead in Compressed App-V Packages
April 25, 2011 1 Comment
The purpose of this white paper is to publicize the performance test data gathered when App-V sequences are compressed in comparison to when the default sequencing option “Not Compressed” is chosen during the sequencing process.
It is quite obvious that the purpose of the compression is to reduce the size of the App-V package either in order to ensure that the maximum 4GB size limitations on the SFT file is not exceeded or to reduce the network traffic that will be generated due to the streaming of App-V package.
Since network capacity and utilization are not constant parameters in organizations, the impact of App-V streaming on network is deemed out of scope. Hence, an App-V stand-alone mode was used in order to explore the impact of package compression on the time to launch.
A Microsoft Windows 7 (32 bit) systems has been used for the purpose of the testing and AppTimer (from PassMark) used for the purpose of recording the application launch times.
Hopefully, this white paper will answer some of your questions regarding the potential disadvantages of sequence compression.
Carry on sequencing.