linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: linux-raid@vger.kernel.org
Subject: Re: SSD + Rust as raid1
Date: Sat, 08 Jun 2013 13:11:38 -0400	[thread overview]
Message-ID: <51B365CA.6090409@tmr.com> (raw)
In-Reply-To: <20130608162235.7ca32f4d@natsu>

Roman Mamedov wrote:
> On Fri, 07 Jun 2013 18:23:56 -0400
> Bill Davidsen <davidsen@tmr.com> wrote:
>
>>> If I have to have a bitmap file, it is
>>> presumably faster to have a larger chunk size
>> If you want performance I think a too big chunk size will hurt you.
> You are confusing the general array chunk sizes, and the bitmap chunk size. In
> the latter, a larger size will universally give better performance (up to some
> value, where it will perhaps start to flat out).
>
If that were the case, then a bitmap would not be used, you could just have a 
single bit, and make the chuck size the size of everything. Since that would 
pretty much make the bitmap worthless, it suggests to me that there is in fact a 
limit to the optimal chunk size, short of what the implementation max allows. I 
think the optimal size is determined by usage, but there is probably some way to 
measure it. I find that when it seems a "if some is good more is better" 
approach fits a problem, I like to check that taking it to the limit would make 
sense. The Latin IIRC is 'reducto ad absurbum' and has saved me from occasional 
wretched excess.

-- 
Bill Davidsen <davidsen@tmr.com>
   We are not out of the woods yet, but we know the direction and have
taken the first step. The steps are many, but finite in number, and if
we persevere we will reach our destination.  -me, 2010



  reply	other threads:[~2013-06-08 17:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 21:23 SSD + Rust as raid1 Dominic Raferd
2013-05-31  0:22 ` Mathias Burén
2013-05-31  7:02   ` Dominic Raferd
2013-05-31  7:30 ` Roman Mamedov
2013-05-31  7:47   ` Dominic Raferd
2013-05-31  7:54     ` Roman Mamedov
2013-05-31  8:52       ` Dominic Raferd
2013-06-04  8:13         ` Dominic Raferd
2013-06-07 22:23           ` Bill Davidsen
2013-06-08 10:22             ` Roman Mamedov
2013-06-08 17:11               ` Bill Davidsen [this message]
2013-06-08 21:58                 ` Roberto Spadim
2013-06-10  8:57                   ` Dominic Raferd
2013-06-01  0:25   ` Stan Hoeppner
2013-06-01  1:19     ` Keith Keller
2013-06-01  4:37       ` Stan Hoeppner
2013-06-07 22:16       ` Bill Davidsen
2013-06-01  1:30     ` Sam Bingner

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=51B365CA.6090409@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rm@romanrm.ru \
    /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).