Re: I/O wait question/scenario

bordenm_at_methodisthealth.org (bordenm_at_methodisthealth.org) wrote:
> Ok, here is the scenario. We have an application, clinical, that the
> db server is having pretty high I/O wait. It can be as high as 50 to
> 60%, but it is not consistently like this. It is more consistently
> around 30 to 40 during busy times. This is running on a p690 regatta
> attached to a shark. The partition is set up with 7procs and 16gig of
> ram. After the vendor has researched this a little, they have said the
> the I/O wait will go down once we add more users to the application.
> They are saying that the I/O wait is high because the processesors are
> so fast that it processes the transactions faster than what it can
> handle. Like I said, they say that the I/O wait will go down once we
> make the runqueues go up by adding more users to the application. To
> me, this doesn not sound correct.
>
> My question is, could this theory be correct?

The I/O wait as reported by what?

> If it is correct,
> doesn't that mean that we have an I/O bottle neck period and it should
> be resolved?

Could it simply mean that whatever tool you are using to report I/O wait considers "SQL*Net message from client" waits to be an I/O wait?

Xho

-- 
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service                        $9.95/Month 30GB