Doc #59928 [Opn->Csd]: APC: Clarification of ttl documentation

From: Date: Tue, 24 Oct 2017 08:48:43 +0000
Subject: Doc #59928 [Opn->Csd]: APC: Clarification of ttl documentation
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-15159@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=59928&edit=1 ID: 59928 Updated by: kalle@php.net Reported by: michalcharemza at gmail dot com Summary: APC: Clarification of ttl documentation -Status: Open +Status: Closed Type: Documentation Problem Package: APC Operating System: Linux PHP Version: 5.3.6 -Assigned To: +Assigned To: kalle Block user comment: N Private report: N New Comment: With APC dead, I don't this is something anyone will ever work on as no stable version of PHP today are supported by APC Previous Comments: ------------------------------------------------------------------------ [2012-04-17 16:49:19] rpamfil at gmail dot com I was confused by the terminology too, but I think that you just need to interpret idle as 'not used', where used = created/modified, or accessed. So a read(hit) will reset the counter, and a write(put) will also do so. ------------------------------------------------------------------------ [2011-09-01 05:54:25] michalcharemza at gmail dot com Description: ------------ It is unclear from the documentation from which point in time the ttl settings are used. Is it from the time the cache entries are created or modified, or from the last time they are accessed? The documentation uses the phrase "idle in a slot", but does not specify what it means for an entry to "idle". i.e. does the act of accessing, but not modifying, an entry count as an action that stops idling? The settings in question are: apc.ttl apc.user_ttl ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=59928&edit=1

« previous php.doc.bugs (#15159) next »