Over time Hotspot and the JIT will convert the interpreted code into native code using profiling information.
随着时间的流逝，Hotspot和JIT会根据收集的信息将解释型代码转化为本机代码。
But performing a task with interpreted code and performing it with compiled code can take significantly different amounts of time.
但是使用解释后的代码执行任务和使用编译后的代码执行任务在时间上有巨大的差异。
Let's say you're going to time 200,000 iterations through a loop, and the compiled code is 10 times faster than the interpreted code.
假设您正在通过循环计时200,000次迭代，编译代码比解释代码快10倍。
A second disadvantage is that AOT-compiled code, though faster than interpreted code, can be substantially slower than JIT-compiled code.
第二个缺点是，尽管AOT编译过的代码比解释过的代码执行速度快，但是却比JIT编译的代码慢得多。
The advances in hardware allow interpreted code to run faster today than compiled code on some systems available when I started work on Bash.
就Bash而论，硬件的进步使今天的解释型代码运行速度快于当初我开始工作时可用的一些系统上的编译型代码。
AOT code is native code and generally executes faster than interpreted code (although it is not likely to run as fast as JIT-generated code).
AOT代码是原生代码，执行速度通常比解释的代码快(但是不太可能像JIT生成的代码那么快)。
Depending on the compilation time and how much faster the compiled code is than the interpreted code, small changes in the number of iterations can result in big differences in measured "performance."
根据编译时间和编译代码比解释代码快的程度，即使对迭代数量只做很小的变化，也可能造成测量的“性能”有极大差异。
Interpreted languages always have an advantage over compiled languages because they can execute code at times that compiled languages can't.
解释语言始终比编译语言具有更大的优势，因为它们可以执行编译语言无法执行的代码。
Even if the file is protected on the server, because the code is interpreted locally it would be foolish to assume that it cannot be gotten.
即使该文件在服务器上是受保护的，但因为代码是在本地解释的，所以以为无法得到这个文件是愚蠢的。
Or, in the case of interpreted languages, the debugger may interpret code directly.
或者，在使用解释语言的情况下，调试器可以直接解释代码。
Code that is interpreted still needs to be handled by the existing trace or hook based debuggers.
解释的代码仍旧需要由现有的基于跟踪或者回调的调试器处理。
The instructions for this complexity are contained within the cell's genetic code, but how this information is accessed, read and interpreted is influenced by development and differentiation.
这个复杂机器的说明书就在细胞的遗传密码中，然而如何接入，理解和解释这些信息都受到发育和分化的影响。
All data, including dynamic SQL statements, user input data, user output data, and character fields in the SQLCA, is interpreted based on this code page.
所有数据，包括动态sql语句、用户输入数据、用户输出数据以及SQLCA中的字符字段，都是基于该代码页进行解释的。
However, the way that URLs are interpreted and mapped in the native code differs between platforms.
然而，解释url的方法及在本机代码的映射对于不同的平台来说是不同的。
AOT-compiled code, on the other hand, starts much higher than interpreted performance but is unlikely to be as high as can be achieved via the JIT compiler.
另一方面，AOT编译代码启动时的性能比解释的性能高很多，但是无法达到JIT编译器所能达到的最高性能。
The compiler runs at less predictable times, the JVM switches from interpreted to compiled code at will, and the same code path may be compiled and recompiled more than once during a run.
编译器运行的次数很难预测，JVM按照自己的想法从解释代码切换到编译代码，而且在运行期间，相同的代码路径可能编译、重新编译不止一次。
Instead, the code is either interpreted or dynamically compiled by the JIT.
相反，这些代码将会由JIT解释或动态编译。
A dynamic compiler mitigates this cost by eventually compiling all the interpreted methods that are frequently called by JIT compiled code, but without a dynamic compiler, this cost can't be hidden.
动态编译器通过最终编译所有由JIT编译代码频繁调用的那些解释过的方法来减少这项开销，但是如果不使用动态编译器，则这项开销就不可避免。
Rt applications can also derive an important benefit from AOT-compiled code: more-deterministic performance that exceeds interpreted performance.
RT应用程序也能从AOT编译代码中获得重要的收益：更具确定性的性能超过了解释的性能。
The JVM interpreted the bytecodes rather than compiling them to machine code and executing the machine code directly.
JVM解释字节码，而不是把字节码编译成机器码并直接执行机器码。
As an interpreted scripting language, it is very friendly to iterative development — there's no recompiling after a single change, and you can see the impact of your code changes in real time.
作为一种解释性的脚本语言，它非常适用于重复开发——不需要在做出个别更改后重新编译，并且能够实时看到更改代码后的效果。
To do that, I can take advantage of the fact that PHP is an interpreted language by storing PHP code in a queue in the database, then executing it later.
为此，可以利用一个事实：PHP是一种解释型语言。可以将PHP代码存储在数据库中的队列中，以后再执行它。
Canonicalization is the method in which raw data is interpreted to have Spaces displayed as Spaces and not as ASCII code.
规范化是解释原始资料以使空格显示为空格而不显示为ascii码的方法。
PHP code isn't compiled; rather, it's interpreted at run time.
PHP代码不经过编译，而是在运行时加以解释。
It's more advanced, however, providing many optimizations that allow interpreted byte code to run nearly as fast (sometimes faster) than precompiled code.
但是它更先进，提供许多优化措施，使得已解释的字节代码几乎与预编译的代码运行得一样快(有时更快)。
Each full-text query term needs to be interpreted correctly by your query code.
查询代码需要正确地解释每个全文查询词。
If JIT is disabled JVM starts quickly but in most cases runs slowly as all byte-code is being interpreted.
如果JIT被禁用了，那么JVM启动会很快，但是在大部分情况中，运行程序的速度都会与解释字节码的速度一样慢。
Pure interpreted, where all code gets parsed on the device and executed with our AST-walking interpreter logic.
纯解释，所有的代码在设备上完成了解析并且通过我们的AST -walking解释逻辑执行。
As you saw in the December installment, the HotSpot JVM first executes a code path in interpreted mode, and only compiles it to machine code after a certain amount of execution.
在12月份的文章中可以看到，HotSpotJVM首先以解释的方式执行代码路径，然后在经过一定量的执行后，才将其编译成机器代码。
It can't be compiled, executed, or interpreted, thus being "reduced to the level of mere documentation" and adding "no more value to a project than an elaborate code comment".
U ML不能被编译、执行或解释，那它就“只剩文档编制的作用”，而且“对项目来说，除了作为详尽的代码注释外别无他用”。
应用推荐