Re: disk i/o balancing - response

The more I/O channels the better for larger systems. On my HP T500 200GB database I had the machine loaded with 18 I/O Channels. This way you can help direct the I/O of your application. Now if I can just find a tool to help me monitor 18 I/O channels realtime, and move I/O dynamically!

fF you consider an HP platform a K-series machine works quite well since you can have 3 I/O channels.

Steve Lemme
DBA
Motorola

In article <5de5tm$9t8_at_lal.interserv.com>, <scheuric_at_sprynet.com> wrote:

> I think that you should be breaking up data and indexes separately over
> as many channels.. Don't break up based on io hits at the system level as
> you may actually start to degredate your system. It is better to stripe your
> data over as many disks and channels as possible and then place your
> indexes on a separate controller and do the same to them. By monitoring
> for hot files, you should be able to determine what tables are getting hit the
> most, and if necessary isolate those or stripe them futher.
>
> Sheilah Scheurich
> Dimension Systems Inc
> DBA
>
> My opinions are my own and that of my employer.
 

-- 
When you are in it up to your ears....
Keep your mouth shut!
rp1399_at_email.sps.mot.com