This value provides a fail-safe in the event that a server process dies while executing a cached source file; if that source file is modified, the memory allocated for the old version will not be reclaimed until this TTL reached.
Set to zero to disable this feature. On by default, but can be set to off and used in conjunction with positive apc. If any pattern matches the source filename, the file will not be cached. The - case is the default, so it can be left off. Leaving it undefined will force an anonymous mmap. On very busy servers whenever you start the server or modify files you can create a race of many processes all trying to cache the same file at the same time.
This option sets the percentage of processes that will skip trying to cache an uncached file. Or think of it as the probability of a single process to skip caching. For example, setting apc. So, the higher the setting the greater the defense against cache slams. Setting this to 0 disables this feature.
Deprecated by apc. When a file is modified on a live web server it really ought to be done in an atomic manner. That is, written to a temporary file and renamed mv the file into its permanent position when it is ready. Many text editors, cp , tar and other such programs don't do this. This means that there is a chance that a file is accessed and cached while it is still being written to.
This apc. The default is 2 seconds, which means that if the modification timestamp mtime on a file shows that it is less than 2 seconds old when it is accessed, it will not be cached. The unfortunate person who accessed this half-written file will still see weirdness, but at least it won't persist. If all of the webserver's files are atomically updated, via some method like rsync which updates correctly , this protection can be disabled by setting this directive to 0.
Mostly for testing and debugging. Prevent files larger than this value from getting cached. Defaults to 1M. Size Should be suffixed by M for megabytes, G for gigabytes. Enabling this option will reduce the amount of memory used per PHP-FPM worker as strings will be stored once rather than for each worker. The optimization level.
Zero disables the optimizer, and higher values use more aggressive optimizations. Expect very modest speed improvements. This is experimental.
A "hint" about the number of distinct source files that will be included or requested on your web server. Set to zero or omit if unsure; this setting is mainly useful for sites that have many thousands of source files. Just like apc. Set to zero or omit if not sure. The number of seconds a cache entry is allowed to idle in a slot in case this cache entry slot is needed by another entry. Leaving this at zero means that APC's cache could potentially fill up with stale entries while newer entries won't be cached.
In the event of a cache running out of available memory, the cache will be completely expunged if ttl is equal to 0. Otherwise, if the ttl is greater than 0, APC will attempt to remove expired entries.
The number of seconds that a cache entry may remain on the garbage-collection list. This value provides a fail-safe in the event that a server process dies while executing a cached source file; if that source file is modified, the memory allocated for the old version will not be reclaimed until this TTL reached. Set to zero to disable this feature.
On by default, but can be set to off and used in conjunction with positive apc. If any pattern matches the source filename, the file will not be cached.
The - case is the default, so it can be left off. Leaving it undefined will force an anonymous mmap. On very busy servers whenever you start the server or modify files you can create a race of many processes all trying to cache the same file at the same time.
This option sets the percentage of processes that will skip trying to cache an uncached file. Or think of it as the probability of a single process to skip caching. For example, setting apc. So, the higher the setting the greater the defense against cache slams. Setting this to 0 disables this feature.
Deprecated by apc. When a file is modified on a live web server it really ought to be done in an atomic manner. That is, written to a temporary file and renamed mv the file into its permanent position when it is ready. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta. The APC source contains a php script that is useful for monitoring and tuning the performance of your cache.
Note: Once you have successfully installed APC, move this file to a password protected area for security.
You can configure the APC monitoring script to use Moodle security. Create a new file apc.
0コメント