Why do I need an Econo JIT?

I learned that the Econo JIT is not optimized for an environment compiling IL other than Normal JIT. In addition, it does not create a machine code cache for the next execution, which means that every time a PE starts up, the JIT will compile IL again into machine instructions.

I was confused why then it is possible to choose compilation in Econo Jit. Also, is there a choice of JIT to be selected in Visual Studio? or do I need to compile through a tooltip if I want to select the difference in JIT mode?

+4
source share
1 answer

The idea behind Econo JIT is to spend less time compiling so that the startup delay is lower for interactive applications. This is actually what you want as soon as you notice that it takes a few seconds to start the application. .NET startup time is already not so slow (also Java :)).

In server-side applications, you want the opposite: you want the perfect code and are ready to wait, because you are probably warming up the application before connecting it to the load balancer. You send an automatic GET to your homepage and other important pages to download and compile.

AFAIK Econo JIT deprecated with .NET 2.0. There is no more choice (with the exception of disabling all optimizations that are a variant of the nuclear bomb).

0
source

All Articles