Why PHP’s JIT Matters: Boosting Performance in PHP 8.0

To date, PHP remains the most popular server‑side language for building websites, holding over 80% of the market share worldwide. The language continues to evolve, with the next major milestone being PHP 8.0 and its Just‑In‑Time (JIT) compilation.

The current stable branch is PHP 7.0, a landmark release that dramatically increased performance and reduced memory usage. Subsequent minor releases 7.1 (2016) and 7.2 (2017) added further features.

PHP 8.0’s exact launch date has not been announced, but community speculation on Twitter suggested a September 2021 release.

2021‑09‑23 #PHP 8 release date. @Savara predicts it! #SymfonyCon – Larry Garfield (@Crell)

PHP’s Real‑Time Compilation Engine (JIT)

JIT is an optimization technique that compiles code at runtime, a method popularized by the Java Virtual Machine (JVM) and Google’s V8 JavaScript engine. While powerful, it is not a silver bullet.

PHP implements a Zend VM that translates human‑readable scripts into opcode instructions during compile time. At runtime, the Zend VM executes these opcodes.

Traditionally, compile‑time and runtime are separate. Bytecode caches such as APC and OPcache store compiled opcodes. JIT removes the distinct compile‑time phase, merging it with runtime to produce machine code on the fly.

In PHP, JIT treats the Zend VM’s opcodes as an intermediate representation, then translates them into architecture‑specific machine code that runs directly on the CPU, bypassing the Zend VM for that portion of execution.

Since PHP 7.0, performance gains have come from optimizing core data structures (e.g., HashTable), enhancing certain opcodes, and improving OPcache’s optimizer. However, these optimizations are approaching their limits, making JIT the most promising avenue for further speed improvements.

The official vote on adding JIT was recently approved, so PHP 8 will include JIT support.

Benchmarks show that JIT brings noticeable speedups for CPU‑intensive workloads, but typical PHP applications like WordPress or Joomla are I/O‑bound, so the impact is minimal in those cases.

PHP programs are often limited by I/O operations—database queries, cache reads/writes, file and socket access—rather than CPU processing.

An example of CPU‑intensive PHP code is Zend/bench.php.

Consequently, JIT’s greatest benefits appear in mathematical or other CPU‑heavy domains. For a deeper dive into PHP JIT, see https://blog.krakjoe.ninja/2019/03/php-gr8.html .

Conclusion

Both JIT and PHP 8.0 are set to become key features of PHP’s future. However, PHP’s short request‑lifecycle is less ideal for JIT compared to long‑running languages like Node.js or Java.

Compiled by: 老夏 Source: Aggregated from foreign media, Open Source China, etc.