r2946 update dbsetup
r2947 update dbupgrade
Did you try to change the columns in the existing index to see if this makes a change?
Do you have good timing values of the old state, as two indexes also mean double work for the database to update the 2nd index too. And it uses more tablespace.
Initial one-off test: loading the metric tab for a 450member group (5charts)took a bit over 2mins
Changes have been applied, not the final answer, but looks like an improvement.
question as to why we created a new index when we already had a scheduleId/timestamp index.
Oracle is saying add an index on timestamp.
need to re-investigate this based on new performance numbers
rev4989 - remove schedule_id index on raw tables;
add time_stamp index on raw tables;
Assigning to Joseph who is working on migrating our perf branch fixes to /trunk
rev5087 - remove schedule_id index on raw tables, which is redundant with the composite index already on those respective tables;
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1448