ModX Caching

I’m developing a site that will have a document count of about 3500 regularly updated pages, coupled with various browse pages that sort the regularly updated (once a day) pages accordingly - using Ditto.

I guess my questions are:

- Is there a way to get ModX to automatically cache (using the existing cache system) the pages containing the Ditto calls by some user-defined time, say, every hour?
- Or, because my cached documents are furthest from the trunk i.e. root-->browse-->sub-browse-->cached doc, is there a way to set the Ditto containing browse pages to cached, to automatically update their cache when a child page has been saved or created?

It is just that I’m finding the Ditto browsing pages to be quite resource intensive and would like to have them in a cache, however if the child pages are updated, I would like the Browse page caches to be updated too. Any suggestions on how to best go about caching site content?

Or is it best to keep the pages dynamic and use something like MySQL Query Cache or Memcached instead?
What might be the best way to integrate Modx with something like Memcached http://www.php.net/memcache?

Cheers

mark

I believe Ditto 1.1 will address a lot of performance issues. What kind of site is this?

It’s an events listing site.

I’m currently using Ditto 1.1 Beta incidentally. Still in the midst of tweaking stuff, so I’m sure I can get a lot performance out of it. Just wondering what other people’s experiences are.

Quote from: mjarecki at Sep 28, 2006, 07:26 PM

Or is it best to keep the pages dynamic and use something like MySQL Query Cache or Memcached instead?
What might be the best way to integrate Modx with something like Memcached http://www.php.net/memcache?

More synchronicity -- and, I wasn’t gonna say anything and hopefully surprise everyone a little more, but I just checked-in the beginnings of an object/result-set caching system to the xPDO project yesterday (xPDO is the new foundation I’ve been using to author the MODx 1.0 code base) that can use any caching technique you want. But my initial implementation is indeed using memcache when available on the platform, falling back to a quick and dirty file-based implementation that performs pretty well, especially with an opcode cache like eAccelerator. I haven’t been able to test the memcache implementation properly yet, but the potential it holds is staggering. I’m pretty excited anyway about the relatively good performance of the file-based cache and the huge reduction in database load this approach offers.

Ultimately, the best solution includes a combination of a trimmed down MODx site cache, the familiar partial page caching, and these object/result-set caching features, or alternatively, there is a very ingenius static page caching technique tillda has come up with (still experimental) that utilizes mod_rewrite to search for static html files in a specific directory before executing MODx at all (see http://modxcms.com/forums/index.php/topic,5912.0.html for more info on tillda’s static file solution).

I can’t wait!

So when do you reckon you’ll have it all complete? Next week possible?