Optimizing PHP Performance with Opcode Caching and Bytecode Preloading

By Alessandro D.P.2 min readFebruary 9, 2026

Understanding Opcode Caching

When a PHP script is executed, the interpreter parses the source code, compiles it into opcodes (the internal representation of the code), and then executes those opcodes. This process is repeated on every request, which can be resource-intensive. Opcode caching stores the compiled opcodes in shared memory, allowing subsequent requests to bypass the parsing and compilation steps.

PHP 7 and later versions come with a built-in opcode cache known as OPcache. Enabling and properly configuring OPcache can drastically reduce execution time and memory usage.

To enable OPcache, configure your php.ini file with the following settings:

opcache.enable=1
opcache.memory_consumption=128
opcache.interned_strings_buffer=8
opcache.max_accelerated_files=4000
opcache.revalidate_freq=60

These settings allocate memory for the cache, define the number of files to cache, and control how often the cache is checked for updates.

Enabling Preloading in PHP 7.4+

Starting with PHP 7.4, you can further optimize performance using bytecode preloading. Preloading allows you to load PHP scripts into memory at server startup, so they are already compiled and cached before handling any requests. This is particularly useful for frameworks and libraries that are used in every request.

To enable preloading, set the following in your php.ini:

opcache.preload=/path/to/preload.php

The preload.php file should contain opcache_compile_file() calls for all the classes or files you want to preload. For example:

<?php
opcache_compile_file('/var/www/vendor/autoload.php');
opcache_compile_file('/var/www/app/Bootstrap.php');
opcache_compile_file('/var/www/app/Config/Database.php');

Preloading can reduce the latency of the first request and eliminate per-request compilation overhead entirely for preloaded files.

Measuring Performance Gains

To quantify the benefits of opcode caching and preloading, you can use tools like ApacheBench (ab) or Siege to perform load testing. Here’s a comparison of execution time and memory usage for a simple PHP script with and without OPcache enabled:

Scenario	Avg. Execution Time (ms)	Memory Usage (MB)
Without OPcache	120	15
With OPcache	30	5
With OPcache and Preloading	20	4.8

These results show a significant reduction in both execution time and memory consumption when OPcache and preloading are used together.

Best Practices for Opcode Caching and Preloading

Monitor OPcache Memory Usage: Use the opcache_get_status() function to check how much memory is being used and how many scripts are cached.
Avoid Preloading Too Many Files: While preloading is powerful, it increases server startup time and memory consumption. Only preload the most critical classes or files.
Use Absolute Paths in Preload Files: Ensure all paths in your preload script are absolute to avoid resolution issues.
Set Appropriate Revalidation Frequency: Set opcache.revalidate_freq to a value that balances performance with the need to reflect code changes.
Use Opcache Status Page for Debugging: Enable the opcache.enable_cli and opcache.status directives to access the status page via the command line or web for monitoring.

Advanced Configuration for Production

In production environments, consider the following advanced settings in php.ini for optimal performance:

opcache.enable=1
opcache.enable_cli=0
opcache.memory_consumption=256
opcache.interned_strings_buffer=16
opcache.max_accelerated_files=10000
opcache.revalidate_freq=2
opcache.fast_shutdown=1
opcache.preload=/var/www/preload.php

These settings increase memory allocation, reduce revalidation frequency, and enable fast shutdown mode, which reduces memory usage during script exit.

Common Pitfalls and Troubleshooting

Cache Invalidation Issues: If you’re not seeing updated code, check opcache.revalidate_freq and ensure it’s set appropriately for your development workflow.
High Memory Usage: If OPcache consumes too much memory, reduce opcache.memory_consumption or limit the number of preloaded files.
Preload Script Errors: Ensure your preload script does not include runtime logic or dependencies that are not yet available at server startup.