The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Catalin(ux aka Dino) BOIE" <util@deuroconsult.ro>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Strange vmstat output. 2.6.10 Scheduler?
Date: Tue, 1 Feb 2005 11:49:49 +0100	[thread overview]
Message-ID: <20050201104949.GM4137@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0502011243270.26221@webhosting.rdsbv.ro>

On Tue, Feb 01 2005, Catalin(ux aka Dino) BOIE wrote:
> >Well then that is why, the writes are taking quite a while to reach the
> >platter. Nothing is wrong, the drive is just slow :-)
> >
> >-- 
> >Jens Axboe
> 
> I don't know what to say because sometimes works really good.
> bi=20000.

The vmstat you showed had bi and bo at the same time, so it's not so
surprising if bi often suffers if it is seeking all over the map to
write out the big chunk submitted.

How does it look with write cache enabled?

> I'm fighting with this problem for 1 month now and I realy tried to 
> resolve the problem.

If postgres uses fsync() properly, you should be safe with write cache
enabled.

> P.S. I tried also with cfq and see no improvement.

Not surprising, there's not much the io scheduler can do for you here.

-- 
Jens Axboe


  reply	other threads:[~2005-02-01 10:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01 10:21 Strange vmstat output. 2.6.10 Scheduler? Catalin(ux aka Dino) BOIE
2005-02-01 10:26 ` Jens Axboe
2005-02-01 10:36   ` Catalin(ux aka Dino) BOIE
2005-02-01 10:42     ` Jens Axboe
2005-02-01 10:46       ` Catalin(ux aka Dino) BOIE
2005-02-01 10:49         ` Jens Axboe [this message]
2005-02-01 10:54           ` Catalin(ux aka Dino) BOIE
2005-02-01 10:59           ` Catalin(ux aka Dino) BOIE
2005-02-01 10:34 ` Massimo Cetra
2005-02-01 10:48   ` Catalin(ux aka Dino) BOIE

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=20050201104949.GM4137@suse.de \
    --to=axboe@suse.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=util@deuroconsult.ro \
    /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