Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
improve value foropcache.max_accelerated_files#21605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:6.4
Are you sure you want to change the base?
Conversation
javiereguiluz commentedNov 29, 2025
This is true ... but readinghttps://www.php.net/manual/en/opcache.configuration.php#ini.opcache.max-accelerated-files seems that not all primes are valid. It must be one of this specific set:
|
opcache.max_accelerated_filesSpomky commentedNov 29, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Correct, except 1048793 that is greater than 1,000,000 and |
According to Paul Dragoonis' talk delivered at the SymfonyCon yesterday, using a non-prime number forces PHP to calculate the next one, adding a small overhead.
References:
I'm not sure if we want to also add a note in Symfony doc to explain the reason