JIT Compilation — Explained with Examples

Just-in-time (JIT) compilation is a technique where code is compiled to native machine code during execution rather than before. JIT combines the flexibility of interpreters (platform independence, dynamic typing) with the performance of ahead-of-time compiled code.

A JIT compiler typically starts by interpreting bytecode (or quickly compiling it with a baseline compiler) while profiling which code paths are executed most — these are “hot” paths. The JIT then recompiles those hot paths to highly optimized native machine code. This adaptive optimization can sometimes outperform static compilation because the JIT uses runtime profiling data. The Java HotSpot VM, V8 (JavaScript), and .NET RyuJIT are prominent JIT compilers.

Real-world analogy. JIT compilation is like simultaneously writing, practicing, and perfecting a speech. You start by reading from notes (interpretation). As you notice certain phrases you say often (hot code), you memorize and refine them (compile). Occasionally you stumble on a rare word (cold code) and glance at your notes again.

Example (JIT optimization — inline caching in V8):

function add(a, b) { return a + b; }

// First call: JIT compiles with type feedback
add(1, 2);
// JIT sees both args are integers → emits optimized integer add
// Later call with different types: deoptimization
add("hello", " world");  // Falls back to generic path

Related terms: AOT Compilation, JVM, V8 Engine, Compiled vs Interpreted, CLR