Bug 1319811 - [scale] - inefficent SQL queries when using datetime filter
Summary: [scale] - inefficent SQL queries when using datetime filter
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ovirt-engine-dwh
Classification: oVirt
Component: Database
Version: 3.6.2
Hardware: x86_64
OS: Linux
unspecified
high vote
Target Milestone: ovirt-4.0.0-rc
: ---
Assignee: Shirly Radco
QA Contact: Eldad Marciano
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 15:06 UTC by Eldad Marciano
Modified: 2016-06-28 21:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-02 12:05:44 UTC
oVirt Team: Metrics
sradco: ovirt-4.0.0?
rule-engine: planning_ack?
rule-engine: devel_ack?
pstehlik: testing_ack+

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

Description Eldad Marciano 2016-03-21 15:06:29 UTC 
Description of problem:
there is lot of queries which using datetime \ history_datetime filte.

seems like we can recursively made a change \ optimize those set of queries.
so, beacuse of that we can handle this in one Bug.

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

How reproducible:
100%

Steps to Reproduce:
1.idle run on large scale env.

Actual results:
long queries.

Expected results:
optimized queries 

Additional info:
Comment 3 Yaniv Lavi 2016-03-23 12:57:55 UTC 
What improvement are you suggesting?
Comment 4 Sandro Bonazzola 2016-05-02 09:56:24 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 6 Yaniv Lavi 2016-05-05 09:54:23 UTC 
What improvement are you suggesting?
Comment 7 Yaniv Lavi 2016-05-23 13:17:46 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 8 Yaniv Lavi 2016-05-23 13:24:17 UTC 
oVirt 4.0 beta has been released, moving to RC milestone.
Comment 9 Yaniv Lavi 2016-06-02 12:05:44 UTC 
Please reopen if you can provide the needed info.
Note You need to log in before you can comment on or make changes to this bug.