As with any Java-based web application, you can sometimes improve performance by assigning particular values to the Java Virtual Machine options. You may want to do this especially if you run into OutOfMemory exceptions in your On-Premise web nodes, or if your kern.log file shows errors like:
- page allocation failure
In such situations, you have the option to either lower your JVM memory settings or increase the physical memory on your server.
Before attempting to adjust the JVM memory settings, you should:
- Get an estimate of daily average page views using the community usage dashboard.
- Consult the deployment sizing and capacity planning guide to estimate how much memory your nodes require.
This solution applies to On-Premise instances only.
You can edit the JVM minimum and maximum memory settings on a node by editing the values for the
jvm_heap_min variables from the command line. These values are expressed in MB. For example, to set the minimum and maximum heap available on the web application node to 4GB, from the command line interface you would type the following:
jive set webapp.jvm_heap_max 4096
jive set webapp.jvm_heap_min 4096
The default JVM values for each of the nodes are listed in Startup Property Reference. The command settings are listed in Startup Properties Commands. Note that your particular community may need to decrease or increase the default values depending on the size and traffic of your community. For sizing capacity recommendations, be sure to read Deployment Sizing and Capacity Planning.
|Jive Web Application(s)||To ensure that the appropriate resources are available to the running application, we recommend setting
environment, these min and max values should be
the same for all of the web application nodes. For larger communities, that is, communities that get more
than 100,000 page views per day or that contain a large amount of content (more than 100,000 messages,
documents or blog posts), you may need to increase
the JVM heap min and max settings to be both 4096
or both 6144.
|Additional Cluster Nodes (if your configuration includes these optional nodes)||These values should match those of the primary web
|Cache Server(s) (if your configuration includes these optional nodes)||None.|
|Document Conversion (if you have this optional module)||We recommend not changing the default settings.
They have consistently performed well in all pre-release quality, stress, and performance tests.