What is Compaction?
As part of the complete analysis of your application, it is possible to determine unneeded elements. The compaction, or pruning, process can then remove all the unused classes, methods, instance variables, design time metadata, and actual bytecode to produce a much smaller application. In addition, correctly applied obfuscation techniques such as PreEmptive’s patented Overload Induction can have a compacting effect. Due to its heavy reuse of identifier names, it saves significant space. Note: This entire process is performed on bytecode, not source. The size reduction caused by compaction is staggering. Some customers have reported a 70% size reduction in their executable. We imagine those customers use large third party libraries that were heavily trimmed. In our tests, we see a solid 30-40% shrinking in many applications.
As part of the complete analysis of your application, it is possible to determine unneeded elements. The compaction or pruning process can then remove all the unused classes, methods, instance variables, design time metadata, and actual bytecode to produce a much smaller application. In addition, correctly applied obfuscation techniques, such as PreEmptive’s patented overload induction, can have a compacting effect. Due to its heavy reuse of identifier names, it saves significant space. Note: this entire process is performed on bytecode or MSIL, not source. The size reduction caused by compaction is literally staggering. Some customers have reported a 70% size reduction in their executable. We imagine those customers use large, third party libraries that were heavily trimmed. In our tests, we see a solid 30-40% shrinking in many applications.
