memcache status

Hi drupalnuts. It looks like #224772 is a legitimate bug that needs fixing.

Are you already using APC as an opcode cache? If not that is a huge performance gain. As far as using the APC module on Drupal.org, I don't know if slantview ever got that to be production ready, so I'd check with him.

For now, though, try the dev release of memcache: http://drupal.org/node/116481

It works well. I haven't investigated the bug reported in #224772, but memcache has allowed many many sites to scale beyond the initial limits of their servers.

In the meantime, I've got to get a D6 release of this out the door, and I'll take the opportunity to look at #224772.

Some clarification about APC: APC is a wonderful thing and can be used as both an opcode cache (highly recommended) and a memory cache. The APC module on d.o. does the latter, putting Drupal cache items into APC memory. It is not a memory cache server, though, so each memory cache is local to the web server running it. This means redundant caches. If you're running more than one web server and need 1 memory caching solution, memcache is the one. The cache router project aims to give you some more fine grained control over this by letting some caches go to local APC memory cache while other data goes to a cache server, such as memcache. This would qualify as the ultimate highly tuned server and is really cool, but probably not necessary for most people. In my opinion, memcache is a good workhorse that will satisfy 90% of all the people who need high performance sites.

So, my recommendation: use APC as an opcode cache and memcache for memory cache.

in my experience, memcache is a big performance increase over APC, as it takes the database out of the cache equation.

all of my scalability issues with drupal have been related to the db.

if you break out each cache table into a separate memcache instance, then memcache still provides a substantial performance increase, despite #224772.

even without the wildcard issue, you won't get the full benefit of memcache without breaking out each cache table into a separate instance.

Feel free to ask more questions. I'm closing issues that seem adequately addressed.