From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Raz <raziebe@gmail.com>,
jnelson-linux-raid@jamponi.net, linux-raid@vger.kernel.org
Subject: Re: stripe_cache_size and performance
Date: Mon, 25 Jun 2007 12:48:21 -0400 [thread overview]
Message-ID: <467FF1D5.6080007@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706221110220.4196@p34.internal.lan>
Justin Piszcz wrote:
> I have found a 16MB stripe_cache_size results in optimal performance
> after testing many many values :)
We have discussed this before, my experience has been that after 8 x
stripe size the performance gains hit diminishing returns, particularly
for typical write instead of big aligned blocks, possibly with O_DIRECT.
I would suggest that as a target even on a low memory machine.
Do your tests show similar? I was only able to test three and four drive
setups using dedicated drives.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2007-06-25 16:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 18:28 stripe_cache_size and performance Jon Nelson
2007-06-21 19:42 ` Raz
2007-06-21 23:09 ` Jon Nelson
2007-06-22 15:01 ` Raz
2007-06-22 15:10 ` Justin Piszcz
2007-06-25 16:48 ` Bill Davidsen [this message]
2007-06-25 17:00 ` Justin Piszcz
2007-06-25 18:20 ` Justin Piszcz
2007-06-25 18:21 ` Justin Piszcz
2007-06-25 18:42 ` Justin Piszcz
2007-06-25 19:48 ` stripe_cache_size and performance [BUG with =64kb] Justin Piszcz
2007-06-25 19:49 ` Justin Piszcz
2007-06-25 20:36 ` Justin Piszcz
2007-06-25 20:42 ` Justin Piszcz
2007-06-25 22:12 ` stripe_cache_size and performance Jon Nelson
2007-06-25 22:19 ` Dan Williams
2007-06-25 23:23 ` Jon Nelson
2007-06-25 22:21 ` Justin Piszcz
2007-06-26 13:58 ` Jon Nelson
2007-06-26 14:00 ` Justin Piszcz
2007-06-26 14:16 ` Jon Nelson
2007-06-26 14:37 ` Justin Piszcz
2007-06-26 15:22 ` Jon Nelson
2007-06-26 15:54 ` Justin Piszcz
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=467FF1D5.6080007@tmr.com \
--to=davidsen@tmr.com \
--cc=jnelson-linux-raid@jamponi.net \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=raziebe@gmail.com \
/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.