diff options
| author | Rasmus Lerdorf <rasmus@lerdorf.com> | 2018-03-30 13:24:17 -0700 |
|---|---|---|
| committer | Rasmus Lerdorf <rasmus@lerdorf.com> | 2018-03-30 13:24:17 -0700 |
| commit | aaae3637e026ca561a235321df68d8e7e36fefbd (patch) | |
| tree | 081da8960145729412389d52cae7f92d65e761ea | |
| parent | 76f421dd3a6eb91d848d76a6947546da38b6c564 (diff) | |
| download | php-git-aaae3637e026ca561a235321df68d8e7e36fefbd.tar.gz | |
Better explanation for the opcache.max_wasted_percentage ini setting
since it was pretty confusing before
| -rw-r--r-- | ext/opcache/README | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/ext/opcache/README b/ext/opcache/README index 6f07f7ee58..a71a7b43b2 100644 --- a/ext/opcache/README +++ b/ext/opcache/README @@ -87,7 +87,13 @@ opcache.max_accelerated_files (default "2000") between 200 and 1000000 are allowed. opcache.max_wasted_percentage (default "5") - The maximum percentage of "wasted" memory until a restart is scheduled. + When the cache fills up this setting decides when to actually reset (dump + all entries) it. At the default of 5% it means that if less than 5% of + the entries in the now full cache are wasted/orphaned, then you have a good + active cache. There is no point emptying a cache full of good entries + only to most likely refill it with those same entries. Once more than 5% + of the cache consists of wasted entries, the cache will reset in this + cache-full scenario. This can be set up to as high as 50%. opcache.use_cwd (default "1") When this directive is enabled, the OPcache appends the current working |