VMProtect offers three compilation methods for code protection: Mutation, Virtualization, and Ultra. While I acknowledge that code protection inherently introduces performance overhead, I am keen to understand the extent of this impact. For instance, if a function initially executes in 50ms without protection, could you provide a reference on the approximate execution times when protected using each of the three methods? This information is crucial as my software has high-performance requirements.
Best regards
WenGe
Performance Impact of Protection Modes
Re: Performance Impact of Protection Modes
1. "Mutation" doesn't protect your code against reversing. The goal of this method is changing code signatures.
2. "Virtualization" converts your code to VM instructions. The speed decreases by about 1000 - 10000 times. Don't recommend to use this method for big loops.
3. "Ultra" converts mutated code to VM instructions. The speed is slower than after "Virtualization".
2. "Virtualization" converts your code to VM instructions. The speed decreases by about 1000 - 10000 times. Don't recommend to use this method for big loops.
3. "Ultra" converts mutated code to VM instructions. The speed is slower than after "Virtualization".