I made some tests to compare the execution time of php scripts with and without opcache. I ran a php script that calculates the the prime numbers 1-500,000. In both cases regardless opcache was enabled or not, the execution time ranged 0.9-1.05 seconds.
When opcache was enabled the status clealy showed as ‘cached’:
/home/xxx/public_html/prime2.php hits: 4, memory: 2.92KB, last used: Tue Jun 15 17:32:08 2021
When opcache was disabled,l added to the blacklist
and showed up in the ‘ignored file locations’:
/home/xxx/public_html/prime.php
Every time when enabled / disabled opcache, made a system reboot as well.
So it apparaently makes no difference if opcash is on or off…
I think I would be more surprised if there was a difference. A tiny app running under php-fpm or mod_fcgi is unlikely to benefit notably from the opcache.
Yes that point makes sense. A single instance of one script makes no difference.
I installed ApacheJmeter. I was running 300 threads at once.
The result was even more surprising:
With opcache the average execution time was found to be 18.3 sec
Without opcache the average execution time was only 17.6 sec.
It’s the same explanation I already gave. You didn’t change the thing that I mentioned would make a difference (tiny app). But, I think you’re expecting a much bigger difference than you’ll actually see, even in the ideal circumstance for using opcache. Everything is already cached at several points in the system. FPM or fcgid are already going to run very fast, relatively speaking. PHP 7 also dramatically improved performance in the general case, including parsing and compiling (making the improvement from op caching less pronounced).