Description of problem: Currently we don't set the Java heap size explicitly. This means that the Java virtual machine will use the default size, which may be as large as 1/4th of the total memory of the machine. Steps to Reproduce: 1. Check the amount of virtual memory before and after the change in a scale environment. 2. 3. Actual results: Expected results: Reduce the amount of virtual memory used by DWH. Additional info:
IF you plan to backport to 4.0.z please change the milestone as well.
4.0.6 has been the last oVirt 4.0 release, please re-target this bug.
Sanity done [root ~]# ps aux -ww | grep java ovirt 8790 8.5 11.7 3093244 214004 ? Sl 15:24 0:19 ovirt-engine-dwhd -Dorg.ovirt.engine.dwh.settings=/tmp/tmpldlQmZ/settings.properties -Xms1g -Xmx1g -Xms1g -Xmx1g -classpath /usr/share/ovirt-engine-dwh/lib/*::/usr/share/java/dom4j.jar:/usr/share/java/apache-commons-collections.jar:/usr/share/java/postgresql-jdbc.jar ovirt_engine_dwh.historyetl_4_1.HistoryETL --context=Default
per comment#3 and conversation with scale in other team, sanity is done moving to them
System team in the end did the performence tests, this is the environment: 1. 1 DC 1 CL 1 SD(nfs) 3 rhel hosts 120VMs 2. Multiple CRED actions were executed on the setup as these are stored in dwh 3. No performence issues were found during this period nor afterwards (1 day) Keep in mind this does not inclease performence of dwh, just limit the stack to 1GB which was verified in comment#4. As all the focused components (dwh, dashboard) were working correctly during this period moving to VERIFIED.