Install the opcache extension #162 #439
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
j0k3r
approved these changes
Apr 17, 2025
Member
|
Good idea! |
Member
|
@deviantintegral that's a good catch, I didn't think it was still disabled 😅 thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On my install, I was seeing ~700ms responses to load an article. Turning this on brings them down to 80-100ms.
The opcache extension should really be enabled by default in all installations. Even on locals for development purposes there's no downside.
I thought about additionally enabling
opcache.validate_timestamps, which does affect manually exec'ing into the container and hacking files, but given there's no opcache at all this seems like a good first step.