linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lothar Braun <mail@lobraun.de>
To: jassduec@gmail.com
Cc: linux-admin@vger.kernel.org, linux-config@vger.kernel.org
Subject: Re: High iowait
Date: Tue, 22 Aug 2006 11:38:10 +0200	[thread overview]
Message-ID: <200608221138.15159.mail@lobraun.de> (raw)
In-Reply-To: <3a1eedb70608211931w67f86bccpb383bb0ff8089f45@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

Hi,

On Tuesday 22 August 2006 04:31, jassduec@gmail.com wrote:
> I have a storage raid attached to my linux server running CentOS 4.3
> kernel 2.6.9-39.0.2.ELsmp. My server goes into huge iowait when i try
> to read/write lot of data to the storage device. How can i debug
> whether the problem is with the storage device or some setting of the
> operating system. Is there any known issue with this kernel? How can i
> tune my system to reduce iowait time?

Why should you want to reduce the iowait time? Iowait, as shown by top, means 
afaik that there are some processes waiting for io to complete  and nothing 
else to do for the processor.
If you're running some CPU eating processes while your I/O operations are 
performed, then the iowait value should go down (this is because your CPU can 
then do more sophisticated work than waiting)

Regards,
Lothar

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-08-22  9:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22  2:31 High iowait jassduec
2006-08-22  9:38 ` Lothar Braun [this message]
2006-08-23 16:10   ` jassduec
2006-08-24  1:01     ` terry white
2006-08-24 20:06     ` Art Wildman
2006-08-25 18:59       ` how tell what specific device is sending an interrupt? tom arnall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200608221138.15159.mail@lobraun.de \
    --to=mail@lobraun.de \
    --cc=jassduec@gmail.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=linux-config@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).