[dev] Horde_Cache_Memcache potential problem?

Jan Schneider jan at horde.org
Fri Jan 13 07:50:35 PST 2006


Zitat von Duck <duck at obala.net>:

> On Friday 13 January 2006 15:28, Didi Rieder wrote:
>> If I was thinking right about this (please correct me if I'm wrong),
>> it would be nice to have a more intelligent garbage collection.
>
> You can't.
>
> The only way to do GC is to flush the server or to delete all connected keys.
> But memcache don't provide a list of existing keys so, the only way it would
> be to write down a cache key list. Which is a wastefull operation, not good
> for a cache system.
>
> I suggest you to run a separate memcache demon a another port or to disable
> GC. Since memcache would automatically delete old entries as the memory runs
> out.

Doesn't memcache have its own gc? It can only store a limited amount  
of objects, right? In this case we don't need gc in the cache driver  
at all, as it was only supposed for backends that would otherwise fill  
up.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/


More information about the dev mailing list