Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1408652

Summary:	[scale][performance] Limit DWH heap size
Product:	[oVirt] ovirt-engine-dwh	Reporter:	Shirly Radco <sradco>
Component:	Services	Assignee:	Shirly Radco <sradco>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	bugs, eberman, juan.hernandez, lsvaty, masayag, pstehlik, sradco, ylavi
Target Milestone:	ovirt-4.1.0-beta	Keywords:	Performance
Target Release:	4.1.0	Flags:	rule-engine: ovirt-4.1+ rule-engine: planning_ack+ sradco: devel_ack+ pstehlik: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Until now we did not set the Java heap size explicitly. Consequence: This meant 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. Fix: We added DWH_HEAP_MIN and DWH_HEAP_MAX parameters to the dwh conf file and set it to 1g. Result: The heap size is limited to 1g, and it is configurable.	Story Points:	---
Clone Of:
Clones:	1416427 (view as bug list)		Environment:
Last Closed:	2017-03-16 14:49:56 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Metrics	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1397833, 1405114
Bug Blocks:

Description Shirly Radco 2016-12-26 08:40:58 UTC

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:

Comment 1 Yaniv Lavi 2017-01-04 09:32:57 UTC

IF you plan to backport to 4.0.z please change the milestone as well.

Comment 2 Sandro Bonazzola 2017-01-25 07:56:11 UTC

4.0.6 has been the last oVirt 4.0 release, please re-target this bug.

Comment 3 Lukas Svaty 2017-01-31 14:31:22 UTC

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

Comment 4 Lukas Svaty 2017-02-28 14:24:41 UTC

per comment#3 and conversation with scale in other team, sanity is done moving to them

Comment 5 Lukas Svaty 2017-03-10 09:06:35 UTC

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.