« A tuning case study: The goofy optimizer (9i.x RDBMS) | Main | An Application Tuning Case Study: The Deadly Deadlock »

Yet Another Case Study: The over-commit trap!

plsql tuning:


Its always rewarding to talk about lesser known performance tuning scenarios, which are not all that well appreciated in the DBA or developer world. Ask anyone as to what performance tuning has one worked upon and quite likely, you may hear - Ah well, I made sure the stats gathered were the latest, the right index was being used or I used a hint to use the right index. Typical Answer.

How often do we look at other aspects like the frequencey of commits?

Neither is it good to do commits less frequently, nor is it good to over-commit. Moderation is the key for a happy medium and at times, it can have bearings on performance problems as well.

Read the complete discussion here...


TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/2143

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on January 23, 2007 10:22 PM.

The previous post in this blog was A tuning case study: The goofy optimizer (9i.x RDBMS).

The next post in this blog is An Application Tuning Case Study: The Deadly Deadlock.

Many more can be found on the main index page or by looking through the archives.

Top Tags

Creative Commons License
This weblog is licensed under a Creative Commons License.
Powered by
Movable Type and Oracle