Bug 1190466

Summary:	HEAP_MAX default value as 1G must be changed
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	ovirt-engine-reports	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED ERRATA	QA Contact:	Yuri Obshansky <yobshans>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.5.0	CC:	alonbl, bazulay, dfediuck, didi, ecohen, gklein, jbelka, juan.hernandez, lsurette, mkalinin, mtessun, ratamir, rbalakri, Rhev-m-bugs, sbonazzo, sherold, sradco, yeylon, ylavi, yobshans
Target Milestone:	---	Keywords:	ZStream
Target Release:	3.5.1	Flags:	ylavi: Triaged+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	vt14 rhevm-reports-3.5.1-11.el6ev	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1188972	Environment:
Last Closed:	2015-04-28 18:14:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1188972
Bug Blocks:	1186161, 1193058, 1197441

Comment 1 Yuri Obshansky 2015-02-08 13:09:04 UTC

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.   
https://mojo.redhat.com/docs/DOC-1011650
https://mojo.redhat.com/groups/rhev-m-scalability-performance-team/projects/rhev-m-35-scalability-performance-tests
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.

Comment 2 Yedidyah Bar David 2015-02-08 13:54:46 UTC

Let's continue the discussion on bug 1185411. Current bug is for Reports, which is a somewhat different issue.

Comment 3 Sandro Bonazzola 2015-02-20 11:07:41 UTC

Automated message: can you please update doctext or set it as not required?

Comment 5 Yuri Obshansky 2015-03-04 09:10:06 UTC

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.

Comment 6 Sandro Bonazzola 2015-03-12 12:14:46 UTC

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.

Comment 7 Yuri Obshansky 2015-03-12 13:01:54 UTC

Successfully verified on RHEV-M 3.5.1-0.1 (build vt14).

Comment 8 Oved Ourfali 2015-03-31 07:19:14 UTC

*** Bug 1196062 has been marked as a duplicate of this bug. ***

Comment 10 errata-xmlrpc 2015-04-28 18:14:24 UTC

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.

https://rhn.redhat.com/errata/RHBA-2015-0905.html