Thanks, I assume since I don't see any walk type of functionality in the API, that there's no real way to find out truly how much space one has free after the memcache is full with expired content. What will happen once the cache is full with non-expired content and an add is called? Is the only real way to test for free-space in the memcached to look for errors in reponse to an add, or am I missing something?
<br><br>Gavin<br><br><div><span class="gmail_quote">On 5/7/07, <b class="gmail_sendername">Jason Edgecombe</b> <<a href="mailto:jason@rampaginggeek.com">jason@rampaginggeek.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Gavin M. Roy wrote:<br>> Hello,<br>><br>> Am running memcached in production on a fairly large site and am<br>> noticing that while I'm putting in expirations, the size of the<br>> utilization is growing disproportionately with the expected growth of
<br>> the cache based upon what we implemented it for. By some testing, it<br>> seems that items that are expired from the cache are only removed when<br>> the get request is sent. Is our interpretation of this behavior
<br>> correct, or does content in the cache expire based upon the timestamp<br>> through some internal stack? If it's the later how often does the<br>> daemon run through to get rid of expired content?<br>>
<br>> TIA,<br>><br>> Gavin<br>Hi Gavin,<br><br>That is correct. expired items are only purged when a get request is<br>sent for the expired item or the expired item is cleared because the<br>storage is needed.<br>
<br>Jason<br></blockquote></div><br>