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按照自己的想法从解释代码切换到编译代码，而且在运行期间，相同的代码路径可能编译、重新编译不止一次。
And the third one I want to point out is, whether this is an interpreted versus a compiled language.
我想说的第三件事情是，这个语言是编译语言，还是解释语言。
But performing a task with interpreted code and performing it with compiled code can take significantly different amounts of time.
但是使用解释后的代码执行任务和使用编译后的代码执行任务在时间上有巨大的差异。
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."
根据编译时间和编译代码比解释代码快的程度，即使对迭代数量只做很小的变化，也可能造成测量的“性能”有极大差异。
The file is interpreted, meaning it is compiled and executed in one step. You should get the following output.
文件会被解释，这意味着它会被编译和执行。你会获得如下输出。
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不能被编译、执行或解释，那它就“只剩文档编制的作用”，而且“对项目来说，除了作为详尽的代码注释外别无他用”。
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倍。
On RC machine RC language can be interpreted directly and can run after compiled.
RC语言可以在RC机器上被直接解释，也可以编译后运行。
So, by implementing stored procedure you will gain in time as it's compiled and not interpreted each time like a normal entity framework query.
因此，通过执行存储过程中你将时间作为它的编译和解释每一次像一个正常的实体框架查询增益。
So, by implementing stored procedure you will gain in time as it's compiled and not interpreted each time like a normal entity framework query.
因此，通过执行存储过程中你将时间作为它的编译和解释每一次像一个正常的实体框架查询增益。
应用推荐