From: "Dan Williams" <dan.j.williams@intel.com>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: stripe_cache_size and performance
Date: Mon, 25 Jun 2007 15:19:37 -0700 [thread overview]
Message-ID: <e9c3a7c20706251519u3f6db295n3c653869ecbfbb0c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706251705040.5806@gheavc.wnzcbav.cig>
> 7. And now, the question: the best absolute 'write' performance comes
> with a stripe_cache_size value of 4096 (for my setup). However, any
> value of stripe_cache_size above 384 really, really hurts 'check' (and
> rebuild, one can assume) performance. Why?
>
Question:
After performance goes "bad" does it go back up if you reduce the size
back down to 384?
> --
> Jon Nelson <jnelson-linux-raid@jamponi.net>
Dan
next prev parent reply other threads:[~2007-06-25 22:19 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
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 [this message]
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=e9c3a7c20706251519u3f6db295n3c653869ecbfbb0c@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=jnelson-linux-raid@jamponi.net \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).