From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: High write latency, iowait, slow writes 2.6.9
Date: Wed, 12 Jan 2005 21:20:18 +0000 (UTC) [thread overview]
Message-ID: <cs44ai$oet$1@news.cistron.nl> (raw)
In-Reply-To: 41E4BB99.90908@zanfx.com
In article <41E4BB99.90908@zanfx.com>,
Paul A. Sumner <paul@zanfx.com> wrote:
>I have a new server that during big io tasks, e.g., bonnie++ and
>tiobench testing, becomes very unresponsive. Both bonnie++ and tiobench
>show good read performance, but the write performance lags, max
>latencies are into the *minutes* and it experiences extended high
>iowait. I'm guessing the iowait may not be a real problem. The machine
>is as follows:
Try another IO scheduler (boot with elevator=deadline or elevator=cfq
on the kernel command line)
Mike.
next prev parent reply other threads:[~2005-01-13 1:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 5:54 High write latency, iowait, slow writes 2.6.9 Paul A. Sumner
2005-01-12 21:20 ` Miquel van Smoorenburg [this message]
2005-01-13 6:59 ` Paul A. Sumner
2005-01-13 8:56 ` Jens Axboe
2005-01-13 19:01 ` Paul A. Sumner
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='cs44ai$oet$1@news.cistron.nl' \
--to=miquels@cistron.nl \
--cc=linux-kernel@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