« Case study: How to leverage +LargePages option of J2SE1.5 on Linux hugemem kernel for 11i Oracle Applications java servlet based modules | Main | Yet Another Case Study: The over-commit trap! »

A tuning case study: The goofy optimizer (9i.x RDBMS)

oracle_optimizer:

While it may not be ideal, at times, it may be required to supplement
or coach the CBO to achieve acceptable levels of application
performance.

They say: Tune the application first.
And then, many a times, the CBO behaviour is not predictable or
favourable, inspite of its best intentions or internal hueristic rules
or availability of latest statistics with good sampling percent.

This
is one such example in which Hints had to be used as one of
the last options to improve the performance of a concurrent program.

Read the entire case study here...


TrackBack

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

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 22, 2007 11:59 PM.

The previous post in this blog was Case study: How to leverage +LargePages option of J2SE1.5 on Linux hugemem kernel for 11i Oracle Applications java servlet based modules.

The next post in this blog is Yet Another Case Study: The over-commit trap!.

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