-
Notifications
You must be signed in to change notification settings - Fork 124
Disable OPcache on critical steps, revert requirement previously added #1327
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
Disable OPcache on critical steps, revert requirement previously added #1327
Conversation
014141f
to
97f998d
Compare
97f998d
to
c750fc5
Compare
9f78886
f37f5ea
to
3035c01
Compare
3035c01
to
9c6dde0
Compare
495ee35
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @M0rgan01
Thank you for your PR, I tested it and :
When I have my OPcache.validate timestamp=0, I get :
and when I have my opcache.revalidate freq =100, I get :
Waiting for feedback about this issue on update
Sorry, something went wrong.
3e32b3c
to
94fc3f7
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed by @M0rgan01
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @M0rgan01
Thank you for your PR, I tested it with each case :
- opcache disabled
- op cache enabled and opcache.revalidate_freq = 0 and opcache.validate_timestamps=1
- op cache enabled and opcache.revalidate_freq = 100
- op cache enabled and opcache.validate_timestamps=0
And I still have the same result :
Tested from :
1.7.8.9 to 8.2.1
Because the PR seems to works as expected, It's QA ✔️
Thank you
Uh oh!
There was an error while loading. Please reload this page.