Making Zimbra run on minimal RAM

Revision as of 23:17, 10 March 2008 by Cfremon (talk | contribs) (Performance Tuning moved to Making Zimbra run on 256 MB ram: Initial title too broad -- article is specifically instructions for making Zimbra run on 256 MB ram)

For Performance Tuning Guidelines go to Performance_Tuning_Guidelines_for_Large_Deployments

this is a test

1. Install minimum sets of OS components and disable any unnecessary services.

2. Disable any unnecessary services, such as AntiVirus, AntiSpam, Proxy, and Logger.

3. Increase heap size at your own risk. ex:zmlocalconfig -e tomcat_java_heap_memory_percent=40

Making Zimbra run on 256 MB ram

(Disclaimer: You do all of this at your own risk, I didn't always know what I was doing -- thewizzard)

1. Turn off unnecessary services

As suggested above, you can turn off AntiVirus, AntiSpam, Proxy and Logger.

2. Increase Tomcats heap size

Also suggested above: increase tomcats heap size using this command:

 zmlocalconfig -e tomcat_java_heap_memory_percent=40

3. Lower MySQL memory usage

Change the percentage of the available memory MySQL should use to 15%:

 zmlocalconfig -e mysql_memory_percent=15

4. Change the size of the MySQL table cache

I don't actually really know what this does, but Zimbra felt faster after I changed it:

 zmlocalconfig -e mysql_table_cache=250

5. Change the my.cnf file

Here are the settings to change in the my.cnf file (which can be found at /opt/zimbra/conf):

 threadcache = 5
 maxconnections = 14

6. Change the slapd.conf.in file

This tip is from the page Performance Tuning Guidelines for Large Deployments. Add these two lines to slapd.conf.in (which can also be found at /opt/zimbra/conf):

 threads 8
 idletimeout 5

Please keep in mind that this setup will be a bit slow and you probably shouldn't use it with more than one user.

Jump to: navigation, search