Printable View
Hi Everyone,
In my application I am using SELECT...FOR UPDATE query due to which the CPU utilization is shooting up very fast. Could someone please chip in with some good alternative for the SELECT...FOR UPDATE query so that the CPU utilization could be brought down.
have you actually determined the cause of the cpu shooting up fast?
if you need to lock the record then you are kind of stuck with it arent you
yes you are correct...we need to lock the record for updation.
Various factors have been identified for the high CPU utilization and this query is one of the factors.
Actually we need to cut down the CPU utilization.......and definitely SELECT...FOR UPDATE query consumes a lot of CPU. So i need to know can we replace SELECT...FOR UPDATE with any other logic.
Locking the row won't consume much CPU. It's the SELECT statement itself that will do that. Start by tuning that as you would any other query.