PHP JIT — When It Helps (and When It Doesn't)

Also Known As

TL;DR

Explanation

PHP 8.0 introduced a JIT compiler (tracing and function modes) as an opcache tier. JIT compiles frequently-executed bytecode to native machine code, eliminating Zend VM interpreter overhead. Benchmarks show 2–4x speedups for pure CPU-bound PHP (number crunching, image processing, ML inference). For typical web applications dominated by database and HTTP I/O, JIT provides little measurable improvement — the CPU is rarely the bottleneck. Enable with opcache.jit=tracing and opcache.jit_buffer_size=128M. Profile first to confirm CPU is actually the bottleneck before expecting JIT to help.

Common Misconception

Why It Matters

Common Mistakes

• Enabling JIT and expecting web application speedups — most PHP web apps are I/O bound; JIT helps CPU-bound code.
• Not enabling OPcache first — JIT requires OPcache and builds on top of it.
• Using JIT mode 1255 without benchmarking — different modes (tracing vs function) suit different workloads.
• Not setting opcache.jit_buffer_size — JIT silently does nothing without a buffer allocated.

Code Examples

; php.ini — JIT not configured:
opcache.enable=1
; opcache.jit=1255         ; Missing — JIT disabled
; opcache.jit_buffer_size= ; Missing — required

; Correct for CPU-bound workloads:
opcache.jit=1255
opcache.jit_buffer_size=128M

; php.ini — enable JIT (PHP 8.0+)
; JIT only helps CPU-bound code — not typical web I/O workloads
opcache.enable=1
opcache.jit_buffer_size=128M
opcache.jit=tracing    ; best for most workloads
; options: disable=0, minimal=1205, function=1205, tracing=1254

; Verify JIT is active:
; php -r 'var_dump(opcache_get_status()["jit"]);'

; Good for: image processing, data transformation, scientific computing
; Neutral for: typical Laravel/Symfony request-response (I/O bound)
; Benchmark your specific workload before relying on JIT gains

References

• ↗ https://www.php.net/manual/en/opcache.configuration.php#ini.opcache.jit

Tags

Related Terms