From b3cad4196413a4b3edd79d09c166e4eb0d03fba6 Mon Sep 17 00:00:00 2001 From: Brian Shire Date: Wed, 1 Apr 2009 01:32:04 +0000 Subject: [PATCH] clarify apc.ttl and apc.user_ttl settings affect on cache expunges. bug #16087 git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@278104 c90b9560-bf6c-de11-be94-00142212c4b1 --- reference/apc/ini.xml | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/reference/apc/ini.xml b/reference/apc/ini.xml index c1803a7a32..4aaa0b23e2 100644 --- a/reference/apc/ini.xml +++ b/reference/apc/ini.xml @@ -1,5 +1,5 @@ - +
&reftitle.runtime; &extension.runtime; @@ -320,7 +320,11 @@ needed by another entry. Leaving this at zero means that your cache could potentially fill up with stale entries while newer entries won't be - cached. + 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. @@ -331,10 +335,16 @@ - The number of seconds a user 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 your cache could potentially fill up with stale entries - while newer entries won't be cached. + 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 your 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.