Bug 1329185 - [scale] - big jvm GC cycles while ramp up vms.
Summary: [scale] - big jvm GC cycles while ramp up vms.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 3.6.5.1
Hardware: x86_64
OS: Linux
medium
high vote
Target Milestone: ---
: ---
Assignee: Martin Perina
QA Contact: Eldad Marciano
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-21 11:03 UTC by Eldad Marciano
Modified: 2017-12-22 07:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-25 14:44:49 UTC
oVirt Team: Infra
ykaul: ovirt-4.2?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Eldad Marciano 2016-04-21 11:03:54 UTC 
Description of problem:
engine java heap usage running big GC cycles in size ~1G.
this behavior exist for along time.

see the following report:

further profiling investigation required


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. 1 cluster, 500 hosts, ramp up vms.
2.
3.

Actual results:
big GC cycles

Expected results:
smaller GC cycles might improve the performance such as memory and CPU utilization.

Additional info:
Comment 2 Sandro Bonazzola 2016-05-02 10:06:46 UTC 
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
Comment 3 Yaniv Lavi 2016-05-23 13:21:27 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 4 Yaniv Lavi 2016-05-23 13:24:23 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 7 Yaniv Kaul 2016-07-11 08:43:13 UTC 
Raising severity and priority so we'll get to look at it early in 4.1, wrt scale and performance.
Comment 8 Yaniv Kaul 2017-01-25 14:44:49 UTC 
Closing - for the time being, we don't see how it affects the user experience.
Note You need to log in before you can comment on or make changes to this bug.