From: "Thierry Florac" <thierry.florac@onf.fr> To: "sathya" <python@zeomega.com> Cc: "zope" <zope@zope.org> Sent: Thursday, February 9, 2012 2:58:02 AM Subject: Re: [Zope] enhancements to RAM cache manager product
Hi,
I used RAM cache a while a few months ago on a Zope (3.3.1) install with a ZEO context and didn't notice any problem ; and as far as I know, I don't see any link between them, as cached data is stored in memory and not in the ZEO database.
Thierry thanks for your response. Yes I meant that the cache is local to a node and not visible to the cluster moving to central storage like memcached is what we are looking for.
Actually, I switched to memcached to be able to share cache data (as well as sessions data) between several front-ends. This required just a small interface and two adapters (one to work with a RAM cache and another one to work with memcached).
No problem for me to share experience if you want to work on a dedicated package.
Ok thank you. Maybe we can build a product that is released to the community.
Best regards, Thierry -- Chef de projets internet/intranet Office National des Forêts Direction des Systèmes d'Information 2, Avenue de Saint Mandé 75570 PARIS Cedex 12
Tél. : 01 40 19 59 64 Fax. : 01 40 19 59 85 Mél. : thierry.florac@onf.fr WWW : http://www.onf.fr ----- Original Message ----- Le Wed, 08 Feb 2012 23:42:58 -0600 (CST), sathya <python@zeomega.com> a écrit:
ram cached pages using the ram cache manager product seems to be a nice way to improve response times.
As far as I remember it did not work well with ZEO.
Is there any merit to reengineering this product to use memcached as the backend instead of ZODB/ZEO ?
If so would anyone have an interest to work on this as a funded project ?
It will be great to hear about newer and better solutions as well.