1
- The Zend Optimizer+
2
- ===================
1
+ The Zend OPcache
2
+ ================
3
3
4
- The Zend Optimizer+ provides faster PHP execution through opcode caching and
4
+ The Zend OPcache provides faster PHP execution through opcode caching and
5
5
optimization. It improves PHP performance by storing precompiled script
6
6
bytecode in the shared memory. This eliminates the stages of reading code from
7
7
the disk and compiling it on future access. In addition, it applies a few
@@ -10,7 +10,7 @@ bytecode optimization patterns that make code execution faster.
10
10
Compatibility
11
11
-------------
12
12
13
- This version of Zend Optimizer+ is compatible with PHP 5.2.*, 5.3.*, 5.4.*
13
+ This version of Zend OPcache is compatible with PHP 5.2.*, 5.3.*, 5.4.*
14
14
and PHP-5.5 development branch. PHP 5.2 support may be removed in the future.
15
15
16
16
Quick Install
@@ -31,9 +31,9 @@ Quick Install
31
31
32
32
zend_extension=/...full path.../opcache.so
33
33
34
- NOTE: In case you are going to use Zend Optimizer+ together with Xdebug,
35
- be sure that Xdebug is loaded after Optimizer+ . "php -v" must show Xdebug
36
- after Optimizer+ .
34
+ NOTE: In case you are going to use Zend OPcache together with Xdebug,
35
+ be sure that Xdebug is loaded after OPcache . "php -v" must show Xdebug
36
+ after OPcache .
37
37
38
38
- Restart PHP
39
39
@@ -63,17 +63,17 @@ Configuration Directives
63
63
------------------------
64
64
65
65
opcache.enable (default "1")
66
- Optimizer+ On/Off switch. When set to Off, code is not optimized.
66
+ OPcache On/Off switch. When set to Off, code is not optimized.
67
67
68
68
opcache.memory_consumption (default "64")
69
- The Optimizer+ shared memory storage size. The amount of memory for storing
69
+ The OPcache shared memory storage size. The amount of memory for storing
70
70
precompiled PHP code in Mbytes.
71
71
72
72
opcache.interned_strings_buffer (default "4")
73
73
The amount of memory for interned strings in Mbytes.
74
74
75
75
opcache.max_accelerated_files (default "2000")
76
- The maximum number of keys (scripts) in the Optimizer+ hash table.
76
+ The maximum number of keys (scripts) in the OPcache hash table.
77
77
The number is actually the first one in the following set of prime
78
78
numbers that is bigger than the one supplied: { 223, 463, 983, 1979, 3907,
79
79
7963, 16229, 32531, 65407, 130987 }. Only numbers between 200 and 100000
@@ -83,13 +83,13 @@ opcache.max_wasted_percentage (default "5")
83
83
The maximum percentage of "wasted" memory until a restart is scheduled.
84
84
85
85
opcache.use_cwd (default "1")
86
- When this directive is enabled, the Optimizer+ appends the current working
86
+ When this directive is enabled, the OPcache appends the current working
87
87
directory to the script key, thus eliminating possible collisions between
88
88
files with the same name (basename). Disabling the directive improves
89
89
performance, but may break existing applications.
90
90
91
91
opcache.validate_timestamps (default "1")
92
- When disabled, you must reset the Optimizer+ manually or restart the
92
+ When disabled, you must reset the OPcache manually or restart the
93
93
webserver for changes to the filesystem to take effect.
94
94
The frequency of the check is controlled by the directive
95
95
"opcache.revalidate_freq".
@@ -127,15 +127,15 @@ opcache.enable_file_override (default "0")
127
127
Allow file existence override (file_exists, etc.) performance feature.
128
128
129
129
opcache.optimization_level (default "0xffffffff")
130
- A bitmask, where each bit enables or disables the appropriate Optimizer+
130
+ A bitmask, where each bit enables or disables the appropriate OPcache
131
131
passes
132
132
133
133
opcache.inherited_hack (default "1")
134
134
Enable this hack as a workaround for "can't redeclare class" errors.
135
- The Optimizer+ stores the places where DECLARE_CLASS opcodes use
135
+ The OPcache stores the places where DECLARE_CLASS opcodes use
136
136
inheritance (These are the only opcodes that can be executed by PHP,
137
137
but which may not be executed because the parent class is missing due to
138
- optimization). When the file is loaded, Optimizer+ tries to bind the
138
+ optimization). When the file is loaded, OPcache tries to bind the
139
139
inherited classes by using the current environment. The problem with this
140
140
scenario is that, while the DECLARE_CLASS opcode may not be needed for the
141
141
current script, if the script requires that the opcode at least be defined,
@@ -147,8 +147,8 @@ opcache.dups_fix (default "0")
147
147
Enable this hack as a workaround for "Cannot redeclare class" errors.
148
148
149
149
opcache.blacklist_filename
150
- The location of the Optimizer+ blacklist file.
151
- The Optimizer+ blacklist file is a text file that holds the names of files
150
+ The location of the OPcache blacklist file.
151
+ The OPcache blacklist file is a text file that holds the names of files
152
152
that should not be accelerated. The file format is to add each filename
153
153
to a new line. The filename may be a full path or just a file prefix
154
154
(i.e., /var/www/x blacklists all the files and directories in /var/www
@@ -157,7 +157,7 @@ opcache.blacklist_filename
157
157
1) Directories that contain auto generated code, like Smarty or ZFW cache.
158
158
2) Code that does not work well when accelerated, due to some delayed
159
159
compile time evaluation.
160
- 3) Code that triggers an Optimizer+ bug.
160
+ 3) Code that triggers an OPcache bug.
161
161
162
162
opcache.max_file_size (default "0")
163
163
Allows exclusion of large files from being cached. By default all files
@@ -172,18 +172,18 @@ opcache.consistency_checks (default "0")
172
172
opcache.force_restart_timeout (default "180")
173
173
How long to wait (in seconds) for a scheduled restart to begin if the cache
174
174
is not being accessed.
175
- The Optimizer+ uses this directive to identify a situation where there may
175
+ The OPcache uses this directive to identify a situation where there may
176
176
be a problem with a process. After this time period has passed, the
177
- Optimizer+ assumes that something has happened and starts killing the
177
+ OPcache assumes that something has happened and starts killing the
178
178
processes that still hold the locks that are preventing a restart.
179
179
If the log level is 3 or above, a "killed locker" error is recorded
180
180
in the Apache logs when this happens.
181
181
182
182
opcache.error_log
183
- Optimizer+ error_log file name. Empty string assumes "stderr".
183
+ OPcache error_log file name. Empty string assumes "stderr".
184
184
185
185
opcache.log_verbosity_level (default "1")
186
- All Optimizer+ errors go to the Web server log.
186
+ All OPcache errors go to the Web server log.
187
187
By default, only fatal errors (level 0) or errors (level 1) are logged.
188
188
You can also enable warnings (level 2), info messages (level 3) or
189
189
debug messages (level 4).
0 commit comments