Re: Instance tuning

From: DA Morgan <damorgan_at_psoug.org>
Date: Mon, 25 Jun 2007 08:12:29 -0700
Message-ID: <1182784349.12148@bubbleator.drizzle.com>

Brian Peasland wrote:
> Ana C. Dent wrote:

>> sd2611 <sd2611_at_gmail.com> wrote in news:1182444501.818580.220700
>> @x35g2000prf.googlegroups.com:
>>
>>> Where does the instance tuning fit if we use the below-mentioned order
>>> implementation.
>>> 1. Tune the design.
>>> 2.Tune the application.
>>> 3. Tune memory.
>>> 4. Tune I/O.
>>> 5. Tune contention.
>>> 6. Tune the operating system.
>>>
>>
>> IMO, #3 & #4 are the only 2 which can be tuned by throwing money at 
>> the problem; more hardware, more better.

>
> Really? Maybe I read it differently. :)
>
> Tuning memory can involve making sure you SGA components are sized
> correctly. And tuning I/O can involve making sure that you have spread
> out your highly active segments among multiple disks and controllers.
> This doesn't necessarily mean throwing more hardware at the problem.
>
> Cheers,
> Brian

I read it the way you did Brian. One can also tune networks, for example with Data Guard and Streams by setting SDU at 32K, etc.

But it is not, as the OP assumed, a sequential process. You gather metrics and you tune the identified choke-point.

-- 
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

Received on Mon Jun 25 2007 - 10:12:29 CDT