Настройка во время выполнения
Поведение этих функций зависит от установок в php.ini.
| Имя | По умолчанию | Меняемо | Список изменений |
|---|---|---|---|
| opcache.enable | "1" | PHP_INI_ALL | |
| opcache.enable_cli | "0" | PHP_INI_SYSTEM | |
| opcache.memory_consumption | "64" | PHP_INI_SYSTEM | |
| opcache.interned_strings_buffer | "4" | PHP_INI_SYSTEM | Available since PHP 5.3.0. |
| opcache.max_accelerated_files | "2000" | PHP_INI_SYSTEM | |
| opcache.max_wasted_percentage | "5" | PHP_INI_SYSTEM | |
| opcache.use_cwd | "1" | PHP_INI_SYSTEM | |
| opcache.validate_timestamps | "1" | PHP_INI_ALL | |
| opcache.revalidate_freq | "2" | PHP_INI_ALL | |
| opcache.revalidate_path | "0" | PHP_INI_ALL | |
| opcache.save_comments | "1" | PHP_INI_SYSTEM | |
| opcache.load_comments | "1" | PHP_INI_ALL | |
| opcache.fast_shutdown | "0" | PHP_INI_SYSTEM | |
| opcache.enable_file_override | "0" | PHP_INI_SYSTEM | |
| opcache.optimization_level | "0xffffffff" | PHP_INI_SYSTEM | |
| opcache.inherited_hack | "1" | PHP_INI_SYSTEM | |
| opcache.dups_fix | "0" | PHP_INI_ALL | |
| opcache.blacklist_filename | "" | PHP_INI_SYSTEM | |
| opcache.max_file_size | "0" | PHP_INI_SYSTEM | |
| opcache.consistency_checks | "0" | PHP_INI_ALL | |
| opcache.force_restart_timeout | "180" | PHP_INI_SYSTEM | |
| opcache.error_log | "" | PHP_INI_SYSTEM | |
| opcache.log_verbosity_level | "1" | PHP_INI_SYSTEM | |
| opcache.preferred_memory_model | "" | PHP_INI_SYSTEM | |
| opcache.protect_memory | "0" | PHP_INI_SYSTEM | |
| opcache.mmap_base | NULL |
PHP_INI_SYSTEM |
Краткое разъяснение конфигурационных директив.
-
opcache.enableboolean -
Enables the opcode cache. When disabled, code is not optimised or cached. The setting opcache.enable can not be enabled at runtime through ini_set(), it can only be disabled. Trying to enable it at in a script will generate a warning.
-
opcache.enable_cliboolean -
Enables the opcode cache for the CLI version of PHP. This is mostly useful for testing and debugging.
-
opcache.memory_consumptioninteger -
The size of the shared memory storage used by OPcache, in megabytes.
-
opcache.interned_strings_bufferinteger -
The amount of memory used to store interned strings, in megabytes. This configuration directive is ignored in PHP < 5.3.0.
-
opcache.max_accelerated_filesinteger -
The maximum number of keys (and therefore scripts) in the OPcache hash table. The actual value used will be the first number in the set of prime numbers { 223, 463, 983, 1979, 3907, 7963, 16229, 32531, 65407, 130987 } that is bigger than the configured value. Only numbers between 200 and 100000 are allowed.
-
opcache.max_wasted_percentageinteger -
The maximum percentage of wasted memory that is allowed before a restart is scheduled.
-
opcache.use_cwdboolean -
If enabled, OPcache appends the current working directory to the script key, thereby eliminating possible collisions between files with the same base name. Disabling this directive improves performance, but may break existing applications.
-
opcache.validate_timestampsboolean -
If enabled, OPcache will check for updated scripts every opcache.revalidate_freq seconds. When this directive is disabled, you must reset OPcache manually via opcache_reset(), opcache_invalidate() or by restarting the Web server for changes to the filesystem to take effect.
-
opcache.revalidate_freqinteger -
How often to check script timestamps for updates, in seconds. 0 will result in OPcache checking for updates on every request.
This configuration directive is ignored if opcache.validate_timestamps is disabled.
-
opcache.revalidate_pathboolean -
If disabled, existing cached files using the same include_path will be reused. Thus, if a file with the same name is elsewhere in the include_path, it won't be found.
-
opcache.save_commentsboolean -
If disabled, all documentation comments will be discarded from the opcode cache to reduce the size of the optimised code. Disabling this configuration directive may break applications and frameworks that rely on comment parsing for annotations, including Doctrine, Zend Framework 2 and PHPUnit.
-
opcache.load_commentsboolean -
If disabled, documentation comments won't be loaded from the opcode cache even if they exist. This can be used with opcache.save_comments to only load comments for applications that require them.
-
opcache.fast_shutdownboolean -
If enabled, a fast shutdown sequence is used that doesn't free each allocated block, but relies on the Zend Engine memory manager to deallocate the entire set of request variables en masse.
-
opcache.enable_file_overrideboolean -
When enabled, the opcode cache will be checked for whether a file has already been cached when file_exists(), is_file() and is_readable() are called. This may increase performance in applications that check the existence and readability of PHP scripts, but risks returning stale data if opcache.validate_timestamps is disabled.
-
opcache.optimization_levelinteger -
A bitmask that controls which optimisation passes are executed.
-
opcache.inherited_hackboolean -
In PHP < 5.3, OPcache stores the places where DECLARE_CLASS opcodes used inheritance; when the file is loaded, OPcache then tries to bind the inherited classes using the current environment. The problem is that while the DECLARE_CLASS opcode may not be needed for the current script, if the script requires that the opcode be defined, it may not run.
This configuration directive is ignored in PHP 5.3 and later.
-
opcache.dups_fixboolean -
This hack should only be enabled to work around "Cannot redeclare class" errors.
-
opcache.blacklist_filenamestring -
The location of the OPcache blacklist file. A blacklist file is a text file containing the names of files that should not be accelerated, one per line. Wildcards are allowed, and prefixes can also be provided. Lines starting with a semi-colon are ignored as comments.
A simple blacklist file might look as follows:
; Matches a specific file. /var/www/broken.php ; A prefix that matches all files starting with x. /var/www/x ; A wildcard match. /var/www/*-broken.php
-
opcache.max_file_sizeinteger -
The maximum file size that will be cached, in bytes. If this is 0, all files will be cached.
-
opcache.consistency_checksinteger -
If non-zero, OPcache will verify the cache checksum every N requests, where N is the value of this configuration directive. This should only be enabled when debugging, as it will impair performance.
-
opcache.force_restart_timeoutinteger -
The length of time to wait for a scheduled restart to begin if the cache isn't active, in seconds. If the timeout is hit, then OPcache assumes that something is wrong and will kill the processes holding locks on the cache to permit a restart.
If opcache.log_verbosity_level is set to 3 or above, an error will be recorded in the error log when this occurs.
-
opcache.error_logstring -
The error log for OPcache errors. An empty string is treated the same as stderr, and will result in logs being sent to standard error (which will be the Web server error log in most cases).
-
opcache.log_verbosity_levelinteger -
The log verbosity level. By default, only fatal errors (level 0) and errors (level 1) are logged. Other levels available are warnings (level 2), information messages (level 3) and debug messages (level 4).
-
opcache.preferred_memory_modelstring -
The preferred memory model for OPcache to use. If left empty, OPcache will choose the most appropriate model, which is the correct behaviour in virtually all cases.
Possible values include mmap, shm, posix and win32.
-
opcache.protect_memoryboolean -
Protects shared memory from unexpected writes while executing scripts. This is useful for internal debugging only.
-
opcache.mmap_basestring -
The base used for shared memory segments on Windows. All PHP processes have to map shared memory into the same address space. Using this directive allows "Unable to reattach to base address" errors to be fixed.
Коментарии
It would appear as though the [opcache.enable] setting is indeed NOT PHP_INI_ALL.For changing it within user.ini yields no effect when disabled at global level. user.ini is ignored for that setting.
When using PHP on a windows platform and enabling opcache, you might run into occasional 500 errors. These will appear to show up entirely random.
When this happens, your windows Event log (Windows Logs/Application) will show (probably multiple) entries from Zend OPcache with Event ID 487. Further information will state the following error message: "Base address marks unusable memory region".
This issue can be resolved by adding the following to your php.ini:
opcache.mmap_base = 0x20000000
Unfortunately I do not know the significance of the value "0x20000000". I can only tell you that this value works to solve the problem (Tried and tested)
The optimization levels as of php 7.3 are the following:
#define ZEND_OPTIMIZER_PASS_1 (1<<0) /* CSE, STRING construction */
#define ZEND_OPTIMIZER_PASS_2 (1<<1) /* Constant conversion and jumps */
#define ZEND_OPTIMIZER_PASS_3 (1<<2) /* ++, +=, series of jumps */
#define ZEND_OPTIMIZER_PASS_4 (1<<3) /* INIT_FCALL_BY_NAME -> DO_FCALL */
#define ZEND_OPTIMIZER_PASS_5 (1<<4) /* CFG based optimization */
#define ZEND_OPTIMIZER_PASS_6 (1<<5) /* DFA based optimization */
#define ZEND_OPTIMIZER_PASS_7 (1<<6) /* CALL GRAPH optimization */
#define ZEND_OPTIMIZER_PASS_8 (1<<7) /* SCCP (constant propagation) */
#define ZEND_OPTIMIZER_PASS_9 (1<<8) /* TMP VAR usage */
#define ZEND_OPTIMIZER_PASS_10 (1<<9) /* NOP removal */
#define ZEND_OPTIMIZER_PASS_11 (1<<10) /* Merge equal constants */
#define ZEND_OPTIMIZER_PASS_12 (1<<11) /* Adjust used stack */
#define ZEND_OPTIMIZER_PASS_13 (1<<12) /* Remove unused variables */
#define ZEND_OPTIMIZER_PASS_14 (1<<13) /* DCE (dead code elimination) */
#define ZEND_OPTIMIZER_PASS_15 (1<<14) /* (unsafe) Collect constants */
#define ZEND_OPTIMIZER_PASS_16 (1<<15) /* Inline functions */
Source: https://lxr.room11.org/xref/php-src%40master/ext/opcache/Optimizer/zend_optimizer.h
It should be noted that according to the original RFC (https://wiki.php.net/rfc/preload) `opcache.preload` caches preloaded files *forever* for all instances of the underlying PHP process.
That means, that hosting multiple websites on the same server might result in some unexpected behaviour.
Concrete example:
- you have a Symfony 3.2 App (which might be an endpoint of some type) and a Symfony 3.4 App (which might be your main application)
- both apps have a main Class called App that is in the same namespace (as it is usual, since the class name is unique to each project)
- depending on which app is loaded first, one or the other will work, since `opcache.preload` has no file based distinction of what class is used where and simply provides them to the user space
This is avoidable by simply not preloading user space classes or, if you work with FPM, by defining a pool for each app.
In order to optimize memory consumption, you might also use a common FPM Pool for all Symfony 3.4 Apps and preload the entire framework in there and simply not preload user space classes (which might be cached by opcache anyway but is slower, since it will be checked if the file has changed on every request).
If you try to allocate more memory that is available using opcache.memory_consumption PHP stops working without any logs to help on debugging. This issue took me 4 hours to solve when creating a staging server with same configrations and less memory that was available on production server.Despite the set of values for opcache.max_accelerated_files including the value 1048793, the maximum as stated is 1000000. If you select a number above 1000000 the value is set its default which is 10000.When opcache.use_cwd=0 include/require of relative paths from different directories will both resolve to the same (first) file.
Example dir structure:
app1
index.php
lib.php
app2
index.php
lib.php
both index.php(s):
include "lib.php";
app1/lib.php:
echo "app1";
app2/lib.php:
echo "app2";
both will echo "app1".