Feb 6, 2014 at 9:14 AM
Am I getting right, NGEN and MPGO won't work with libz?
Feb 20, 2014 at 12:42 PM
Never tested. To be honest as far as I understand ngen has little to none to negative performance impact.

Wikipedia: "NGen is intended to make the assembly execute faster by removing the JIT compilation process at runtime, but this does not always improve performance because some optimizations can be done only by a JIT compiler (e.g., if the JIT compiler knows that the code is already running with full trust, it can skip certain expensive security checks). Because of this fact, it makes sense to use NGen only after benchmarking the application performance before and after it."

I understand MPGO is meant to fix this problem.

As I said I never tested it I can only guess. And my guess is:

They won't crash or anything but they will only ngen the very top assembly (executable) not the .dlls inside. So potential benefit is close to zero. You could unpack .dlls than ngen them, then delete them. If they are all strongly typed .NET should use NGENed versions BEFORE it goes to LibZ resolver.