I have spent the better part of the last week configuring and tweaking the caching for our Magento store and it is working great on my dev install. I have Tinybrick s Lightspeed and Speedbooster extensions along with some customizations. It does full page caching and properly flushes the correct tags when I edit a product so that only the pages affected get flushed. I initially set it up using file caching and only just switched it over to Memcached. On my local dev server, this is still working great. When I put it on the remote dev server running in the same environment as our live site, this doesn t work as expected. For the most part it is good, but when I edit a product, I have to flush the entire cache to see the change. After doing some research I have learned that Memcached doesn t support flushing by matching tag...or at least that s what I understood from the Zend documentation:
Be careful : with this backend, "tags" are not supported for the moment as the "doNotTestCacheValidity=true" argument.
另外,如果你看一下档案的来源<代码>。 Zend/Cache/Backend/Memcastal.php in the However, on my local dev server, it seems to be working fine, which I really can t explain. So that begs the question, "Why?". Are there differences in versions of the Zend Framework or PHP that may affect this? My local dev server is running the following: PHP 5.3.3-1ubuntu9.6 with Suhosin-Patch (cli) (built: Oct 14 2011 22:31:25)
Copyright (c) 1997-2009 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Our dev/live server is running this: PHP 5.2.17 (cli) (built: Jun 13 2011 14:23:24)
Copyright (c) 1997-2010 The PHP Group
Zend Engine v2.2.0, Copyright (c) 1998-2010 Zend Technologies 这难道不是差别吗? 是否有这方面的经验? 如果这实际上是一种框架限制,是否知道围绕什么工作? 或者,我只是做了一些错误的事情吗? Thanks!clean/
case Zend_Cache::CLEANING_MODE_MATCHING_TAG:
case Zend_Cache::CLEANING_MODE_NOT_MATCHING_TAG:
case Zend_Cache::CLEANING_MODE_MATCHING_ANY_TAG:
$this->_log(self::TAGS_UNSUPPORTED_BY_CLEAN_OF_MEMCACHED_BACKEND);
break;