From my experience, "log fils sync" has been always caused by either
application (increasing commit rate or increasing amount of redo -
like heavy batches in the extream case) or IO performance.
Fiddling with priorities is not that simple and I would first get
proof that there is a problem that can be solved with priority change.
At least, if there is no CPU bottleneck than I wouldn't even look at
it (someone please correct me if I am wrong here).
2006/7/12, Johnson, George <GJohnson_at_gam.com>:
...
> After doing a little reading up I came across Steve Adams' note on process priorities with regards the background processes. Opinion seems to be divided on whether it's wise to place the BG procs into real-time and leave user process in shared? The only concern I have is that profiling would need to be introduced into the DB to try to stop the job/schedule J00x BG processes getting carried away.
...
> The other question I have for Solaris admins on the list, would process priorities be remembered by process signature across process restarts? Ie if you shutdown the DB the LGWR process will get a new process ID on each restart, so would the Solaris O/S remember and keep hampering the LGWR process based on what it remembered about it before?
...
--
Best regards,
Alex Gorbachev
http://blog.oracloid.com
--
http://www.freelists.org/webpage/oracle-l
Received on Wed Jul 12 2006 - 03:51:54 CDT
