为什么我需要的Econo JIT？ [英] Why Do I need Econo JIT?

问题描述

我研究了JIT的Econo没有为编译IL，比正常JIT不同的环境进行了优化。此外，它不会产生机械code缓存为下执行，这意味着 每次PE运行时，JIT编译再次将IL为机器指令。

I studied that Econo JIT is not optimized for the environment compiling the IL, different than the Normal JIT. Also, it doesn't create machine code cache for the next execution, which means every time the PE runs, the JIT compiles the IL into machine instructions again.

我很困惑，为什么会一个选择编译的Econo日新即可。此外，有没有JIT的选择，在Visual Studio中进行选择？或者我应该通过及时编译，如果我要选择不同的JIT模式？

I am confused why would One choose to compile in Econo Jit then. Also, is there a choice of JIT to be chosen in Visual Studio? or should I compile through prompt if I want to choose difference JIT mode?

推荐答案

的Econo JIT的想法是花更少的时间进行编译，使启动延时较低的交互式应用程序。这实际上是你想一旦你发现应用程序需要几秒钟来启动什么。 .NET启动时间increadibly已经慢（所以是Java的:)）。

The idea of Econo JIT is to spend less time compiling so that startup latency is lower for interactive applications. This is actually what you want once you notice the app takes seconds to start up. .NET startup time is increadibly slow already (so is Java's :) ).

在服务器端的应用程序，你想要的恰恰相反：你想完美的code和愿意等待，因为你可能热身你的应用程序反正之前将其连接到负载平衡器。你发出自动进入网页和其他重要的网页，让他们载入和编译。

In server-side apps you want the opposite: You want perfect code and are willing to wait because you probably warm-up your app anyway before connecting it to the load-balancer. You issue an automatic GET to the homepage and other important pages to get them loaded and compiled.

AFAIK的Econo JIT是因为.NET 2.0过时。没有选择的余地了（除了禁用所有优化这是核弹选项）。

AFAIK Econo JIT is obsolete since .NET 2.0. There is no choice anymore (except for disabling all optimizations which is the nuclear bomb option).

这篇关于为什么我需要的Econo JIT？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！