Back to bug 1397833

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-11-23 12:38:50 UTC Keywords FutureFeature
Shirly Radco 2016-11-23 12:42:02 UTC CC juan.hernandez
Lukas Svaty 2016-11-23 12:44:42 UTC CC lsvaty, sradco
Flags needinfo?(sradco)
Yaniv Kaul 2016-11-23 15:52:22 UTC Keywords Performance
Severity unspecified high
Yaniv Kaul 2016-12-01 14:26:07 UTC Target Milestone ovirt-4.1.0-alpha ovirt-4.1.0-beta
Flags needinfo?(sradco)
Yaniv Lavi 2016-12-06 15:26:41 UTC CC ydary
Yaniv Lavi 2016-12-07 15:36:20 UTC Keywords FutureFeature
Component RFEs ETL
Summary [RFE] Improve dwh resources consumption Improve dwh resources consumption
Yaniv Lavi 2016-12-15 10:25:30 UTC Keywords Tracking
CC rhev-integ-dev
Component ETL Trackers
Version 4.0.1 ---
Product ovirt-engine-dwh ovirt-distribution
Summary Improve dwh resources consumption [Tracker] - Improve dwh resources consumption
Shirly Radco 2016-12-15 14:27:59 UTC Status NEW ON_QA
Red Hat Bugzilla Rules Engine 2016-12-15 14:28:04 UTC Flags planning_ack? planning_ack+
Shirly Radco 2016-12-15 14:28:33 UTC Keywords TestOnly
Shirly Radco 2016-12-15 16:03:08 UTC Blocks 1405114
Shirly Radco 2016-12-15 16:04:32 UTC Status ON_QA NEW
Shirly Radco 2016-12-19 10:22:56 UTC Keywords TestOnly
Shirly Radco 2016-12-26 08:40:58 UTC Blocks 1408652
Shirly Radco 2017-01-08 12:00:39 UTC Depends On 1411100
Shirly Radco 2017-01-08 12:19:14 UTC Depends On 1411100
Yaniv Kaul 2017-01-15 16:11:00 UTC Target Milestone ovirt-4.1.0-beta ovirt-4.1.1
Flags needinfo?(sradco)
Shirly Radco 2017-01-16 09:13:33 UTC Status NEW ON_QA
Flags needinfo?(sradco)
Pavel Stehlik 2017-01-16 09:20:41 UTC QA Contact pstehlik lsvaty
Flags testing_ack? testing_ack+
Red Hat Bugzilla Rules Engine 2017-01-16 09:20:47 UTC Flags ovirt-4.1? ovirt-4.1+
Sandro Bonazzola 2017-01-19 08:45:19 UTC Target Release --- 4.1.0
Target Milestone ovirt-4.1.1 ovirt-4.1.0-rc
Shirly Radco 2017-01-23 09:28:54 UTC Doc Text Feature:
DWH configuration was updated to allocate 1 GB of RAM.

Added 2 new java args to ovirt-engine-dwhd.conf.in:
DWH_HEAP_MIN=1g
DWH_HEAP_MAX=1g

Reason:
We didn't set the Java heap size explicitly. This means that the Java virtual machine would use the default size, which may be as large as 1/4th of the total memory of the machine.

Result:
Now the process may take up to 1G RAM and can be set higher for large environments using the new parameters.
Doc Type If docs needed, set a value Enhancement
Emma Heftman 2017-03-02 15:38:10 UTC CC eheftman
Doc Text Feature:
DWH configuration was updated to allocate 1 GB of RAM.

Added 2 new java args to ovirt-engine-dwhd.conf.in:
DWH_HEAP_MIN=1g
DWH_HEAP_MAX=1g

Reason:
We didn't set the Java heap size explicitly. This means that the Java virtual machine would use the default size, which may be as large as 1/4th of the total memory of the machine.

Result:
Now the process may take up to 1G RAM and can be set higher for large environments using the new parameters.
Previously, the Java heap size for the Data Warehouse was not explicitly set, resulting in the Java virtual machine using the the default size, which may have been as large as a quarter of the machine’s total memory. In this release, the Data Warehouse’s configuration was updated to allocate 1 GB of RAM, with the addition of two new parameters:
DWH_HEAP_MIN=1g
DWH_HEAP_MAX=1g

The size can be set to a higher value for larger environments using these new parameters.
Megan Lewis 2017-03-07 02:12:35 UTC CC melewis
Doc Text Previously, the Java heap size for the Data Warehouse was not explicitly set, resulting in the Java virtual machine using the the default size, which may have been as large as a quarter of the machine’s total memory. In this release, the Data Warehouse’s configuration was updated to allocate 1 GB of RAM, with the addition of two new parameters:
DWH_HEAP_MIN=1g
DWH_HEAP_MAX=1g

The size can be set to a higher value for larger environments using these new parameters.
Previously, the Java heap size for the Data Warehouse was not explicitly set. This resulted in the Java virtual machine using the default size, which could have been as large as a quarter of the machine’s total memory. With this release, the Data Warehouse’s configuration was updated to allocate 1 GB of RAM, with the addition of two new parameters:
DWH_HEAP_MIN=1g
DWH_HEAP_MAX=1g

The size can be set to a higher value for larger environments using these new parameters.
Lukas Svaty 2017-03-10 09:08:45 UTC Status ON_QA VERIFIED
Megan Lewis 2017-03-14 00:00:32 UTC Doc Text Previously, the Java heap size for the Data Warehouse was not explicitly set. This resulted in the Java virtual machine using the default size, which could have been as large as a quarter of the machine’s total memory. With this release, the Data Warehouse’s configuration was updated to allocate 1 GB of RAM, with the addition of two new parameters:
DWH_HEAP_MIN=1g
DWH_HEAP_MAX=1g

The size can be set to a higher value for larger environments using these new parameters.
Previously, the Java heap size for Data Warehouse was not explicitly set. This resulted in the Java virtual machine using the default size, which could have been as large as a quarter of the machine’s total memory. With this release, Data Warehouse’s configuration was updated to allocate 1 GB of RAM, with the addition of two new parameters:
DWH_HEAP_MIN=1g
DWH_HEAP_MAX=1g

The size can be set to a higher value for larger environments using these new parameters.
Sandro Bonazzola 2017-03-16 14:49:44 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2017-03-16 10:49:44 UTC
Sandro Bonazzola 2017-05-11 09:28:44 UTC CC rhev-integ-dev

Back to bug 1397833