PHP OPcache: Improve Application Performance
PHP normally compiles source files into opcodes before executing them. OPcache can store the compiled bytecode in shared memory so PHP does not need to compile the same files on every request.
Why OPcache Helps
By reusing compiled scripts, OPcache can reduce repeated compilation work and improve response times, especially on applications that execute many PHP files.
Check Whether OPcache Is Enabled
You can inspect loaded PHP modules from the command line, but remember that CLI and web-server PHP may use different configurations.
php -m | grep -i opcache
For the web runtime, inspect the PHP configuration used by the website or a protected diagnostic page. Do not leave a public phpinfo() page online.
Important Configuration Options
Common settings include opcache.enable, opcache.memory_consumption, opcache.interned_strings_buffer, and opcache.max_accelerated_files. The appropriate values depend on the application size and server resources.
On production systems, opcache.validate_timestamps and opcache.revalidate_freq affect how quickly file changes are detected. If timestamp validation is disabled, deployments need a reliable OPcache reset or PHP process restart strategy.
Measure Before Tuning
Benchmark representative pages before and after configuration changes. Check memory usage, cache hit rate, and application response times. Avoid changing several settings at once without measurements.
Deployment Considerations
After deploying changed PHP files, ensure the runtime sees the new code. Depending on the hosting setup and OPcache configuration, this may require a cache reset or PHP-FPM restart.
Conclusion
OPcache is a valuable production optimization, but it is not a substitute for efficient database queries, sensible caching, and profiling. Measure the application and tune settings for the actual hosting environment.