Personal tools
You are here: Home Products CacheFu Roadmap #2: Memcached Support
Document Actions

#2: Memcached Support

Contents
  1. Motivation
  2. Assumptions
  3. Proposal
  4. Implementation
  5. Risks
  6. Progress log
  7. Participants
by Justin Ryan last modified September 30, 2006 - 20:00
CacheFu should support, optionally of course, MemcachedManager, which should be able to significantly improve performance metrics for deployments with multiple ZEO clients working in parallel, especially on the same machine.
Proposed by
Justin Ryan
Seconded by
Helge Tesdal
Proposal type
Architecture
Repository branch
psol
State
being-discussed

Motivation

Memcached has been around for some time and is used in many large-scale dynamic web applications, most notably the LiveJournal open-source blogging website.  Providing an option to use this in place of RAMCache and "stupidcache" for CacheFu could significantly reduce memory usage and duplicate execution overhead when multiple zeo clients are deployed.

Assumptions

The behaviour of tesdal's MemcachedManager branch is assumed to be compatible with RAMCache.

Proposal

CacheFu should be able to take advantage of MemcachedManager in multiple ZEO Client setups.

Implementation

We should clean up PageCacheManager and, if necessary, the cache manager used for Macro Caching, such that they can derive functionality from either of RAMCacheManager or MemcachedManager, based on configuration.

Risks

PageCacheManager as it stands today works, and we might break it.

Progress log

MemcachedManager should be working, but is not integrated into CacheFu.

Participants

Helge Tesdal

Justin Ryan

Geoff Davis


For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by