Skip to Content
Points to reduce high CPU usage
- Perhaps test the process without making the updates to the record to see where slowness is happening. If it is slow when iterating through the records without modifying them, then that would lead to a different investigation path.
- If iterating through index order, it can be slower than in natural order.
- If a the modifications to the record change fields that are indexed, each update is more expensive. If this operation has exclusive access to the tables and you are modifying all/most records, you might consider dropping the indexes involved first and then rebuilding them after the process. That might be faster.
- Perhaps verify that the data translation itself is not causing the high CPU usage. The simple reading and writing of records is not typically a high CPU operation. It is more often limited by disk throughput.