Skip to content

Commit 4b4cd69

Browse files
committed
Better explanation for the opcache.max_wasted_percentage ini setting
since it was pretty confusing before
1 parent ab592df commit 4b4cd69

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

ext/opcache/README

+7-1
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,13 @@ opcache.max_accelerated_files (default "2000")
8787
between 200 and 1000000 are allowed.
8888

8989
opcache.max_wasted_percentage (default "5")
90-
The maximum percentage of "wasted" memory until a restart is scheduled.
90+
When the cache fills up this setting decides when to actually reset (dump
91+
all entries) it. At the default of 5% it means that if less than 5% of
92+
the entries in the now full cache are wasted/orphaned, then you have a good
93+
active cache. There is no point emptying a cache full of good entries
94+
only to most likely refill it with those same entries. Once more than 5%
95+
of the cache consists of wasted entries, the cache will reset in this
96+
cache-full scenario. This can be set up to as high as 50%.
9197

9298
opcache.use_cwd (default "1")
9399
When this directive is enabled, the OPcache appends the current working

0 commit comments

Comments
 (0)