RHEV-M's JVM Heap Size value is very depended on setup (how many Hosts/Storages and VMs). I didn't change default value of 1G during my performance tests and I didn't encounter with Out Of Memory exception in spite of using non-powerful server for engine - 8 CPUs and 16 G RAM. My setup was 1 DC/Cluster/1-2 Hosts/1-2 Storages/ 100-200 VMs.
Please, take a look my last test results to get the full picture.
It will be a great to share customer problematic RHEV-M configuration and setup.
(hardware and software configuratio, RHEV-M Setup - DC/Cluster/Hosts/Storages/VMS).
My opinion is:
- we don't need change default value of 1G. It will be required only on specific configuration which could be done by customer as well.
- we need perform tuning tests and publish tuning tips. There is impossible to test all configurations thus we require an input from our support with customers common used RHEV-M configuration and setup.
Let's continue the discussion on bug 1185411. Current bug is for Reports, which is a somewhat different issue.
Automated message: can you please update doctext or set it as not required?
I think, the current solution did not fully resolve a requirement to set automatically JVM Memory Heap Size.
1. -Xmx and -Xms should be set to a multiple of 1024
i.e. 1024M, 2048M, 3072, 4096, etc.
refer to http://docs.oracle.com/cd/E13222_01/wls/docs81/perform/JVMTuning.html#1110613
2. What about -XX:PermSize=256m -XX:MaxPermSize=256m?
I suppose, that a permanent generation size should be increased accordingly to Heap Size. Definitely, it requires additional tuning to understand how many our application requires memory to load classes and static on start-up.
Need to take in account that summary memory used by engine will be calculate like -Xmx + MaxPermSize and permanent generation won't be garbage collected.
Moving back to on QA since the change requested in the original description of the bug has been fixed.
If further improvement of the automation used for setting automatically JVM Memory Heap Size is needed, please open a new RFE for it.
Successfully verified on RHEV-M 3.5.1-0.1 (build vt14).
*** Bug 1196062 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.