|
Red Hat Bugzilla – Full Text Bug Listing |
| Summary: | Perf: Async deletion of resource slow due to call time data deletion | ||
|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Heiko W. Rupp <hrupp> |
| Component: | Monitoring | Assignee: | RHQ Project Maintainer <rhq-maint> |
| Status: | NEW --- | QA Contact: | Mike Foley <mfoley> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.0.0 | CC: | jshaughn |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Bug Depends On: | |||
| Bug Blocks: | 620933 | ||
This index was never put in place. Still valid, I guess. Maybe not relevant as I thin calltime is moving to cassandra. |
@NamedQueries( { @NamedQuery(name = CallTimeDataKey.QUERY_DELETE_BY_RESOURCES, query = "DELETE CallTimeDataKey ctdk WHERE ctdk.schedule IN ( SELECT ms FROM MeasurementSchedule ms WHERE ms.resource.id IN ( :resourceIds ) )") }) forces the database into full table scans per resource id deleted (actually, only one resource id is passed in, but this does not matter here). Putting an index on rhq_calltime_data_value.key_id speeds up the deletion dramatically (from multiple minutes in my case to several seconds) CREATE INDEX ct_key_index ON rhq_calltime_data_value USING btree (key_id);