Hi!
I've checked in a couple of bug fixes in cvs related to the RAM cache index in CPSPortlets:
- fixes for CMF 1.5 (Action Portlet) support for lazy url references (<...._getURL> in the ActionInformation)
- the 'timeout' cache parameter was no taken into account (now it is taken into account even for the custom parameters set in the Custom Portlet, so it is possible to write 'timeout:60' to store a portlet in the cache for 60 seconds) .
- better support for multilingual sites
- some fine-tuning
the cache parameters are described in skins/cpsportlets_default/getCPSPortletsCacheParams.py and their meaning is explained in doc/cpsportlets-RAMCache-draft.txt - these are meant to be fine-tuned.
if a portlet is not cached properly, a simple fix is to set its cache parameters to 'no-cache' and to rebuild all portlets. (portal_cpsportlets > rebuild). But in any case it is better to store rendered portlets in RAM and avoid as much as possible reading from the ZODB.
what is left to do:
- optimize queries for portlets whose cache validity is based on events. (bug #421 )
/JM _______________________________________________ cps-devel mailing list http://lists.nuxeo.com/mailman/listinfo/cps-devel
