See this http://drupal.org/project/memcache Talk to Robert about it before you duplicate it. On 3/6/07, Steve Rude <steve@achieveinternet.com> wrote:

I have done much testing with memory based object caching using memcached and I think it would be nice if there was the ability to choose what type of caching you wanted (memory/file/db) and have the cache.inc functionality basically an abstraction layer that the storage mechanism can be taken care of by other include files ( e.g. cache-memcache.inc cache-file.inc. The same way that the database abstraction works.

I would be willing to begin some work on this if anyone is interested. We are building a Drupal site now that will need to scale to >30m page views per month and I would like to work within an accepted method to help grow and scale Drupal.

If anyone has any prior work or projects that can be looked at to help get this going down the correct path, please point me in the right direction.

Thanks,

Steve Rude

On 3/6/07, Karoly Negyesi <karoly@negyesi.net> wrote:

...

Hi,

I might be mistaken but I thought file caching was something much sought after. I found posts relating to it as early as 2002.

And yet, when the possibility has arisen for it to happen cleanly (pluggable cache.inc), the code for it has been dumped into CVS on August 26, 2006 and not a single cvs commit since then.

It's not used much according to the issues but that probably has something to do with not having a single release.

Is the community truly interested? If yes, then please a maintainer step up.

And yes, I have contacted the current maintainers three months ago to no avail.

Regards,

NK

--

Steve Rude Lead Web Developer

800-618-8777phone / 858-225-0479 fax www.achieveinternet.com steve@achieveinternet.com

Achieve Internet is a Division of Web Page Maintenance, Inc.

-- 2bits.com http://2bits.com Drupal development, customization and consulting.

On 06 Mar 2007, at 19:41, Steve Rude wrote:

I have done much testing with memory based object caching using memcached and I think it would be nice if there was the ability to choose what type of caching you wanted (memory/file/db) and have the cache.inc functionality basically an abstraction layer that the storage mechanism can be taken care of by other include files ( e.g. cache-memcache.inc cache-file.inc. The same way that the database abstraction works.

A good start would be to rigorously benchmark and compare the different file caching solutions, and to compare them against their database caching alternatives. All the existing file caching modules were originally developed for Drupal 4.7 and simply ported to Drupal 5. It's not clear how well they perform on Drupal 5, or whether they are needed at all. Last time I checked (a couple of months ago before D5 was released), file caching didn't buy me much additional performance over Drupal 5's "aggressive database caching". This observation was in line with my expectations --- I just set out to confirm this. Of course, there will be cases where file caching does buy you something (when the database is the bottleneck?) and it might have some additional advantages (site continues to work a "little bit" when the database is down), but it also has disadvantages (setup cost, less tested, less suitable for multi-tier architectures). I meant to work on such an analysis after I wrote http://buytaert.net/ drupal-5-performance, but I didn't get around to it yet. To me, getting a good overview of the different strategies/solutions is key before pursuing any further work, or before we can recommend one module over another. I still intend to do these benchmarks if no one else does, but it might take me a couple of weeks. If anyone wants to work on this, feel free to though. -- Dries Buytaert :: http://www.buytaert.net/