All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul A. Sumner" <paul@zanfx.com>
To: linux-kernel@vger.kernel.org
Subject: Re: High write latency, iowait, slow writes 2.6.9
Date: Wed, 12 Jan 2005 22:59:52 -0800	[thread overview]
Message-ID: <41E61C68.10801@zanfx.com> (raw)
In-Reply-To: <cs44ai$oet$1@news.cistron.nl>

Thanks... I've tried the as, deadline and cfq schedulers. Deadline is
giving me the best results. I've also tried tweaking the stuff in
/sys/block/sda/queue/iosched/.

For lack of a better way of describing it, it seems like something is
thrashing.

Miquel van Smoorenburg wrote:
> 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.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Paul A. Sumner
Principal Software Engineer

Moore Iacofano Goltsman, Inc. (MIG)
800 Hearst Avenue
Berkeley, CA  94710
Office: 510-845-7549 ext. 191
FAX:   510-845-8750
Mobile: 510-812-1520



  reply	other threads:[~2005-01-13  6:58 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
2005-01-13  6:59   ` Paul A. Sumner [this message]
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=41E61C68.10801@zanfx.com \
    --to=paul@zanfx.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.