public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Stiller <ms@2scale.net>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: howto boost write(2) performance?
Date: Wed, 10 Oct 2007 08:26:27 +0200	[thread overview]
Message-ID: <1191997587.3675.4.camel@blackberry> (raw)
In-Reply-To: <200710092025.34436.nickpiggin@yahoo.com.au>


> 
> The kernel really cannot sustain 125MB/s? I assume the disk
> array is capable?

Yes, the array should be capable, LSI controller U320, SATA disks inside
the array. 

> Where is the bottleneck? Does it keep all disks busy, or are
> the CPUs overloaded?

I'm not sure where the bottleneck is. CPU Load goes up with 
many pdflush processes in D state.

Thanks for the suggestions with sg and O_DIRECT so far, 
will try this.

-Michael




  reply	other threads:[~2007-10-10  6:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 13:50 howto boost write(2) performance? Michael Stiller
2007-10-09 10:25 ` Nick Piggin
2007-10-10  6:26   ` Michael Stiller [this message]
2007-10-09 14:19 ` Gustavo Chain
2007-10-09 14:56 ` Andi Kleen
2007-10-09 15:42   ` Boaz Harrosh
2007-10-09 16:26     ` Michael Tokarev
2007-10-11 13:50   ` Michael Stiller
2007-10-17 22:19 ` Bill Davidsen

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=1191997587.3675.4.camel@blackberry \
    --to=ms@2scale.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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