public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: Dave Pitts <dpitts@cozx.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How can I boost block I/O performance
Date: Sat, 06 May 2006 22:32:52 +0300	[thread overview]
Message-ID: <445CF9E4.3040202@argo.co.il> (raw)
In-Reply-To: <445CE6ED.30703@cozx.com>

Dave Pitts wrote:
> Hello all:
>
> I've been trying some hacks to boost disk I/O performance mostly by 
> changing values
> in the /proc/sys/vm filesystem.  A vmstat display shows bursty block 
> out counts with
> fairly consistent interrupt counts:
>
> procs -----------memory---------- ---swap-- -----io---- --system-- 
> ----cpu----
> r  b   swpd   free   buff  cache   si   so    bi    bo   in    cs us 
> sy id wa
> 4  0    720  80252   1820 7077456    0    0     9   852    5    11  1 
> 14 84  0
[...]
> 5  0    720  90364   1860 7067080    0    0    40 66956 17995 95384  0 
> 17 82  0
>
> This test is running several NFS clients to a RAID disk storage array. 
> I also see the
> same behavior when running SFTP transfers. What I'd like is a more 
> even block
> out behavior (even at the expense of other apps as this is a file 
> server not an app
> server).  The values that I've been hacking are the 
> dirty_writeback_centisecs,
> dirty_background_ratio, etc. Am I barking up the wrong tree?
No  iowait time, plenty of idle time: looks like you are network bound. 
What time of network are you running?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  parent reply	other threads:[~2006-05-06 19:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-06 18:11 How can I boost block I/O performance Dave Pitts
2006-05-06 19:31 ` Jon Smirl
2006-05-06 19:35   ` Avi Kivity
2006-05-06 19:32 ` Avi Kivity [this message]
2006-05-06 21:17   ` Dave Pitts
2006-05-07  5:13     ` Avi Kivity
2006-05-08 15:41       ` Dave Pitts
2006-05-08 15:50         ` Avi Kivity
2006-05-06 23:55 ` Jesper Juhl
2006-05-08 11:18   ` Erik Mouw

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=445CF9E4.3040202@argo.co.il \
    --to=avi@argo.co.il \
    --cc=dpitts@cozx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox