Doc #59928 [Com]: Clarification of ttl documentation
| From: | rpamfil at gmail dot com | Date: | Tue, 17 Apr 2012 16:49:19 +0000 |
| Subject: | Doc #59928 [Com]: Clarification of ttl documentation | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-8271@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
Comment by: rpamfil at gmail dot com
Reported by: michalcharemza at gmail dot com
Summary: Clarification of ttl documentation
Status: Open
Type: Documentation Problem
Package: APC
Operating System: Linux
PHP Version: 5.3.6
Block user comment: N
Private report: N
New Comment:
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.
Previous Comments:
------------------------------------------------------------------------
[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