While there are no concrete rules about configuring heap sizes, there are some basic guidelines that can help prevent performance issues as systems grow. Required heap space will depend on the average load per collector, and can vary greatly in different environments.
|Size (Collectors per MS)||MS Main Heap||MS Exec Heap||Console Heap|
Main MS Heap Space
By default, this heap is 1Gb. In most cases, doubling this value to 2Gb is recommended. Deployments with lots of collectors (hundreds per MS), or systems that have extraordinarily high amounts of transactions may need more heap space to run optimally.Config File:
To increase heap space to 4Gb, you would change the above value to -Xmx4096m, save the change, and restart the MS service for the change to take affect.MS Exec Heap Space
The MS exec heap space is separate from the main heap, and is used for several processor intensive operations such as viewing historical queries. When a historical query is started, FactFinder spawns a separate JVM to do the work so that the MS performance is not impacted. We recommend setting this value to half the size of the main MS heap to begin with.Config File:
/server/config/FactFinderMS.properties on the MS.Setting:
After changing the value, save the change and restart the MS service for the change to take affect.Console Heap Space (Local and WebStart)
There are two types of Console that you can use to access a FactFinder MS. The locally installed console, and the Java WebStart console. Local Console Heap Config File:
-Xmx2048mWebStart Console Heap Config File:
After changing the heap value, save the change and restart the MS service for the change to take affect.