Quote:
|
Originally Posted by KevinH Since all the action/caching is in the server I guess this is where you would want to try to put it in. I'm not sure how much it would help though. We already partition the data similar to memcached. So we don't cache the same object in more than one place like other apps would do. A user's mailbox is on one DB and cached by it's local tomcat instance. |
Yes, we want to implement memcached in the Zimbra server side. What we really want to cache is all the user information stored in LDAP. As I say in this thread
http://www.zimbra.com/forums/showthr...?p=775#post775, we have bad performance problems with LDAP and in our current setup, we use nscd together with memcached to solve them. They help us pretty well, 50-70% LDAP connections are served directly by the local nscd/memcached server. We see no way to use nscd together with Zimbra so only memcached may help.
Our plan is to make memcached become something like zimbra-cached, that means it's will be intergrated to the installer and users can choose whether to install it. If yes, they will be asked for some configuration information (how much RAM, the IP, the port...) and after that Zimbra will automatically be configured to use memcached.
The Java Client API for memcached is available at
http://www.whalin.com/memcached/. We havent used it before but it seems to be in active development. Its license is LGPL.
What should we do? Please advise.
-g