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

Bug 1047150

Summary:	Increace performance for fetching Hosts from database
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Gilad Chaplik <gchaplik>
Component:	ovirt-engine	Assignee:	Liran Zelkha <lzelkha>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Eldad Marciano <emarcian>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4.0	CC:	bazulay, dfediuck, emarcian, gchaplik, gklein, lpeer, lzelkha, mavital, rbalakri, rgolan, Rhev-m-bugs, sherold, yeylon
Target Milestone:	---	Keywords:	CodeChange, Performance
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sla
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-01 14:28:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gilad Chaplik 2013-12-29 13:07:55 UTC

Description of problem:
Currently when scheduling, engine use to fetch all VDS (host) objects by cluster. According to profiling tests conducted lately on scheduling process in engine, this query is very time consuming.

We should think of making this query more light-weighted, and even reduce the times we call it (maybe to aggregate calls to it while validating).

Comment 2 Doron Fediuck 2014-10-29 11:09:00 UTC

Barak,
what's the plan to handle it?

Comment 3 Barak 2014-11-12 21:30:30 UTC

Please specify:
- what exact query are we talking about
- what flow? any run VM will reflect this issue ?

Comment 4 Gilad Chaplik 2014-11-13 09:44:51 UTC

(In reply to Barak from comment #3)
> Please specify:
> - what exact query are we talking about
> - what flow? any run VM will reflect this issue ?

The query was getVdsForVdsGroupWithStatus, but according to latest testing 
(bug 1149701) the query is okay.

I think we should invest time to understand what happens in large scale.

Comment 5 Barak 2014-11-13 15:54:28 UTC

(In reply to Gilad Chaplik from comment #4)
> (In reply to Barak from comment #3)
> > Please specify:
> > - what exact query are we talking about
> > - what flow? any run VM will reflect this issue ?
> 
> The query was getVdsForVdsGroupWithStatus, but according to latest testing 
> (bug 1149701) the query is okay.
> 
> I think we should invest time to understand what happens in large scale.

We investigate what happens in large scales all the time.
I'm afraid that if I don't get a real substance for this bug than I'll close it.
Unless you come up with a specific problem.

Anyway added needinfo on Liran (to keep him in the loop)
And leaving needinfo on you to supply the info.

If nothing comes up this bug will be closed

Comment 6 Doron Fediuck 2014-11-17 16:58:54 UTC

We'll revisit it for 3.6, as we're out of capacity for 3.5 cycle.

Comment 7 Roy Golan 2015-05-27 08:27:11 UTC

Eldad, have you seen this query slow-performing? if not 
then we can close this.

Comment 8 Eldad Marciano 2015-06-01 13:18:03 UTC

No at all,
but there is a open defect for scheduling already see:
https://bugzilla.redhat.com/show_bug.cgi?id=1149701

Comment 9 Barak 2015-06-01 14:28:53 UTC

per comments #7 & #8  closing this bug INSUFFICIENT_DATA.

If you have a clearer scenario please reopen this bug - or a different more specific bug.