Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Opcache settings are too opinionated. #521

Open
aepod opened this issue Mar 4, 2021 · 0 comments
Open

Default Opcache settings are too opinionated. #521

aepod opened this issue Mar 4, 2021 · 0 comments

Comments

@aepod
Copy link

aepod commented Mar 4, 2021

Opcache validate toggled off causes a lot of issues, in lower environments.

While this setting is fine in cloud servers where files don't change local developers do need to be able to see the changes.

;
; Setup opcache configuration
;
opcache.validate_timestamps = 0
opcache.blacklist_filename="${MAGENTO_CLOUD_APP_DIR}/op-exclude.txt"
opcache.max_accelerated_files=16229
opcache.consistency_checks=0

This was introduced in: 8cfcb8f#diff-243dae866e7173c76f8b91864096c15ffcb3aec3699da130eb0b7ef2566fdce3

This is also problematic because of the
opcache.validate_timestamps = 0
opcache.consistency_checks=0

This basically makes it stop checking files for changes, and local development environments end up having to be restarted to see the changes. If this is required in Magento Cloud, and it does make sense to have it there, I would suggest not enforcing it here, but perhaps moving it to a performance settings file (php.performance.ini) that gets included in the cloud environments.

The issues with op-exclude.txt is handled in another ticket: #520

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant