Quote:
|
Originally Posted by KevinH In general we configure MySQL and Tomcat (java) to take a significant % of the total system memory to increase caching. So it's normal to see a large memory footprint for these when you've got so much RAM on the machine. |
I can see some positives and some negatives to this. The main negatives I'm seeing are that on systems where zimbra is not the only thing running zimbra can hog resources since it's set up to, by default, take a significant portion of the available memory. This deprives the other applications of memory and can cause the system to slow to a crawl.
Is there any way to limit the amount of memory zimbra uses?