Bug 534570 (RHQ-1354) - Investigate use of additional indices on tables we purge from
Summary: Investigate use of additional indices on tables we purge from
Keywords:
Status: CLOSED NOTABUG
Alias: RHQ-1354
Product: RHQ Project
Classification: Other
Component: Performance
Version: 1.2
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Joseph Marques
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-13 14:35 UTC by Charles Crouch
Modified: 2015-02-01 23:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Charles Crouch 2009-01-13 14:35:00 UTC 
We should do some investigation into whether our purge process could be improved by having some additional indexes, e.g on the TIME_STAMP columns, on tables we could end up deleting a lot of rows from, e.g. events, 1h, 6h, 1d tables. We obviously need to also make sure that insert performance is not significantly impacted by having to update any new index.
Comment 1 Joseph Marques 2009-01-13 15:30:22 UTC 
i've also seen some table contention issues in the alert subsystem.  if there is load on the system, and you try to update an alert template, it will not always completely successfully.  ugly stack in the ui.
Comment 2 Joseph Marques 2009-09-04 22:05:27 UTC 
duplicate of RHQ-2376, which is already resolved
Comment 3 Red Hat Bugzilla 2009-11-10 20:31:12 UTC 
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1354
This bug is related to RHQ-1336
Note You need to log in before you can comment on or make changes to this bug.