Bug 616746 - Perf: consider putting an index on resource(id,parent_id)
Summary: Perf: consider putting an index on resource(id,parent_id)
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Database (Show other bugs)
(Show other bugs)
Version: 3.0.0
Hardware: All Linux
low
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: rhq-perf
TreeView+ depends on / blocked
 
Reported: 2010-07-21 10:28 UTC by Heiko W. Rupp
Modified: 2014-06-04 19:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-06-04 19:58:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Heiko W. Rupp 2010-07-21 10:28:11 UTC
For things like uninventory of resources, the resource id and parent id are queried.
Putting an index on this will considerably speed up things.

For the long term, some more clever (pre)computation is needed instead of the relatively expensive queries we have today.

See also

https://fedorahosted.org/pipermail/rhq-devel/2010-June/000204.html
https://fedorahosted.org/pipermail/rhq-devel/2010-July/000211.html

Comment 1 Jay Shaughnessy 2014-06-04 19:58:14 UTC
We have individual indexes on ID and PARENT_ID.  I think this is sufficient.


Note You need to log in before you can comment on or make changes to this bug.