Description
This report is based on experimental evidence.
Scenario:
- DB2 9.7
- one process definition with an asnychronous continuation
- one process definition with a timer event that is due far in the future
- 20,000 instances, 5% async jobs, 95% timer jobs
Problem: The resulting DB2 query plan shows that the acquisition query uses a full table scan and none of the indexes we provide.
There should be an index we create by default that all databases use when making an acquisition query.
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is related to
-
CAM-9581 Job acquisition query causes high CPU costs
-
- Closed
-