-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
Setting opcache.validate_timestamps=0
causes all files to display "has been invalidated"
#92
Comments
Hi |
I can confirm, that "has been invalidated" is shown for every entry. However, the hit counter is counting up and my hit rate is 99%. So I asume this is a bug.
|
No, my understanding is that setting this to 0 disables the feature, and thereby all files are cached (which is better performance-wise, as timestamps do not need to be checked) |
@pereorga |
@M-Falken no, these are different options indeed, and I am not confusing them:
So
In the first one, OPcache won't validate timestamps during run-time. In the second one, OPcache won't validate them during compile-time. |
If With opcache.validate_timestamps=1 ...
[scripts] => Array
(
[/tmp/php.php] => Array
(
[full_path] => /tmp/php.php
[hits] => 0
[memory_consumption] => 656
[last_used] => Wed Jul 26 01:44:24 2023
[last_used_timestamp] => 1690335864
[timestamp] => 1690335668
)
)
... With opcache.validate_timestamps=0 ...
[scripts] => Array
(
[/tmp/php.php] => Array
(
[full_path] => /tmp/php.php
[hits] => 0
[memory_consumption] => 656
[last_used] => Wed Jul 26 01:41:14 2023
[last_used_timestamp] => 1690335674
)
)
... |
opcache.validate_timestamps=0
causes all files to display "has been invalidated"
I have the following opcache settings:
This is consistent with the stats I'm seeing:
However, in the "Cached" tab, I see "has been invalidated" on every entry:
Is that correct? My understanding is that all my files should never invalidate.
Also, could anyone confirm that the "last used" date is the date of the last hit? the screenshot included in the readme confuses me a little bit, as it has a date from 1970:
https://camo.githubusercontent.com/ceba44e11a4e8c494ccd65bb72669579e527ca115b1941153a052781c2cdc129/687474703a2f2f616d6e7574732e636f6d2f696d616765732f6f7063616368652f73637265656e73686f742f6361636865642d76332e706e67
The text was updated successfully, but these errors were encountered: