dbKoda for MongoDB

dbKoda for MongoDB - a modern open source database IDE, now available for MongoDB. Download it here!

Next Generation
Databases: NoSQL,
NewSQL and Big Data

Buy at Amazon

Read sample at Amazon

Buy at Apress

Latest Postings:


Oracle Performance Survival Guide

Buy It
Read it on Safari
Scripts and Examples
Sample Chapter


Powered by Squarespace

 MySQL Stored procedure programming

Buy It
Read it on Safari
Scripts and Examples 


« Accessing Oracle from Powershell | Main | Grid control therapy »

Systematic Oracle Performance Tuning

When faced with an obviously IO-bound database, it's tempting to deal with the most obvious (symptom) - the IO subsystem immediately.  Unfortunately, this usually treats symptoms rather the cause, is often expensive and usually futile.  Here's my article on a more systematic approach:

Systematic Oracle tuning (pdf)

and here's the powerpoint from the recent NOCOUG conference.

Reader Comments (1)

Couldn't have been any more correct.

Although on the other hand just adding few more spindles could be the only issue sometimes. As noticed back in 2006: we tuned and tuned and tuned till the last possible sql was bound. Only to get very little positive impact.

Turns out, all our disks were upto 90% full. Although they are high capacity disks, once "a" disk goes beyond certain capacity, performance starts degrading. In our case, we had no choice but to add more spindles to relieve contention.

Never had any issues after bringing them down to about 60% full.

So open for debate?
November 24, 2007 | Unregistered CommenterSejas

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>