非jit编译器获取源代码，并在编译时将其转换为特定于机器的字节代码。JIT编译器获取编译时生成的与机器无关的字节代码，并在运行时将其转换为特定于机器的字节代码。Java使用的JIT编译器允许一个二进制文件无需修改就能在多种平台上运行。

20%的字节码在80%的时间内被使用。JIT编译器获得这些统计数据，并优化这20%的字节代码，通过添加内联方法、删除未使用的锁等，并创建特定于这台机器的字节码来更快地运行。我引用这篇文章，我发现它很方便。http://java.dzone.com/articles/just-time-compiler-jit-hotspot

正如其他人提到的

JIT代表Just-in-Time，这意味着代码在需要时才编译，而不是在运行时之前。

为了给上面的讨论补充一点，JVM维护一个函数执行时间的计数。如果该计数超过预定义的限制，JIT将代码编译为处理器可以直接执行的机器语言(不像一般情况下，javac将代码编译为字节码，然后java -解释器逐行解释这个字节码，将其转换为机器代码并执行)。

另外，下次计算此函数时，将再次执行相同的编译代码，而不像常规解释那样逐行重新解释代码。这使得执行速度更快。

一开始，编译器负责将高级语言(定义为比汇编程序更高级别)转换成目标代码(机器指令)，然后(通过链接器)将其链接成可执行文件。

At one point in the evolution of languages, compilers would compile a high-level language into pseudo-code, which would then be interpreted (by an interpreter) to run your program. This eliminated the object code and executables, and allowed these languages to be portable to multiple operating systems and hardware platforms. Pascal (which compiled to P-Code) was one of the first; Java and C# are more recent examples. Eventually the term P-Code was replaced with bytecode, since most of the pseudo-operations are a byte long.

即时(JIT)编译器是运行时解释器的一个特性，它不是在每次调用方法时都解释字节码，而是将字节码编译为运行机器的机器代码指令，然后调用此目标代码。理想情况下，运行目标代码的效率将克服每次运行时重新编译程序的低效率。

JVM actually performs compilation steps during runtime for performance reasons. This means that Java doesn't have a clean compile-execution separation. It first does a so called static compilation from Java source code to bytecode. Then this bytecode is passed to the JVM for execution. But executing bytecode is slow so the JVM measures how often the bytecode is run and when it detects a "hotspot" of code that's run very frequently it performs dynamic compilation from bytecode to machinecode of the "hotspot" code (hotspot profiler). So effectively today Java programs are run by machinecode execution.

JIT编译器只在第一次执行时将字节码编译为等效的本机代码。在每次连续执行时，JVM仅使用已编译的本机代码来优化性能。

如果没有JIT编译器，JVM解释器将逐行转换字节码，使其看起来就像正在执行本机应用程序一样。

源