Improving PHP Performance with OPcache: Benchmarks, Configuration, and Deployment Strategies

In today’s highly digitalized environment, server‑side caching is essential for achieving excellent performance, especially on high‑traffic platforms where efficient cache strategies ensure rapid responses and improved user experience.

Without proper caching, repeated PHP script execution leads to unnecessary processing delays, analogous to traffic congestion in a busy city.

OPcache acts as an advanced traffic control system, storing pre‑compiled bytecode in shared memory to eliminate the need for PHP to parse scripts on each request, thereby significantly enhancing server performance.

Why Choose OPcache?

OPcache stores compiled script bytecode in shared memory, reducing PHP’s load and parse time per request, shortening response times, and increasing the number of requests a high‑traffic platform can handle per second.

Performance Benchmarking with OPcache

Below is a graphical representation of our benchmark results, obtained using ApacheBench on a sample page.

Initial tests without OPcache yielded a modest ~2.8 requests per second (rps) with the following PHP configuration:

opcache_enabled=0

After Enabling OPcache

Enabling OPcache raised performance to ~5.7 rps using this configuration:

zend_extension=opcache.so
opcache.enable=1
opcache.enable_cli=0
opcache.memory_consumption=96
opcache.interned_strings_buffer=16
opcache.max_accelerated_files=4096
opcache.max_wasted_percentage=5
opcache.validate_timestamps=1
opcache.revalidate_path=0
opcache.revalidate_freq=2
opcache.max_file_size=0

Fine‑Tuned OPcache Settings

Further tuning increased throughput to ~21 rps (approximately ten‑fold improvement) with the following configuration:

zend_extension=opcache.so
opcache.enable=1
opcache.memory_consumption=512
opcache.interned_strings_buffer=64
opcache.max_accelerated_files=32531
opcache.validate_timestamps=0
opcache.revalidate_freq=0
opcache.revalidate_path=0
opcache.save_comments=1

Performance Trade‑offs

Optimizations often involve trade‑offs; disabling certain settings can boost speed but may serve stale code, which is risky for frequently updated high‑traffic sites. Balancing performance and reliability is crucial.

We recommend avoiding or using these settings cautiously in production:

opcache.validate_timestamps=0

Disabling this maximizes performance but may deliver outdated code; enable it if your codebase changes often.

opcache.revalidate_freq=0

This can cause stale bytecode; regular revalidation is advisable for dynamic sites.

opcache.revalidate_path=0

Turning this off prevents OPcache from checking updated scripts in include paths; use with care.

Establishing a Safe Deployment Strategy

When fine‑tuning OPcache, a robust deployment strategy is vital. To avoid serving outdated code, we introduced automated cache‑clearing mechanisms.

Manual Cache Clearing

Manual control can be achieved by executing the opcache_reset() function after deployment, though it carries the risk of being forgotten during urgent releases.

Automated Cache Clearing During Deployment

Automating cache resets ensures the cache is refreshed on each deployment, reducing human error but relying on a stable deployment pipeline.

Scheduled (Fallback) Cache Clearing

Setting up cron jobs to clear OPcache during low‑traffic periods provides a safety net, though it may not be ideal for environments with frequent deployments.

Conclusion

By leveraging OPcache, we increased platform performance from roughly 2.8 rps to an impressive 21 rps—a near ten‑fold boost. While results may vary across environments, OPcache proves to be a powerful tool for PHP performance optimization.