From: John Hughes <john@Calva.COM>
To: Bill Davidsen <davidsen@tmr.com>
Cc: mark delfman <markdelfman@googlemail.com>,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: MD performance options: More CPU’s or more Hz’s?
Date: Mon, 09 Nov 2009 18:37:16 +0100 [thread overview]
Message-ID: <4AF8534C.3030304@Calva.COM> (raw)
In-Reply-To: <4AF8505D.9060007@tmr.com>
Bill Davidsen wrote:
> John Hughes wrote:
>> An external journal can be a huge win for ext3 if you are doing lots
>> of file creates/deletes. (Striped raid, i.e.
>> raid0/raid5/raid6/raid10 doesn't help the journal much as it is used
>> sequentially. In my tests putting the journal on a raid1 and the
>> rest of the fs on a raid10 makes things go much faster. If you have
>> enough disks of course :-))
>
> You might try mounting with data=journal and see what performance you
> get with small reads and writes. Might surprise you. I hadn't thought
> of using raid1 (or raid0 if speed is more important than survival),
> but I have been playing with using SSD just for the journal. As you
> say, when you do lots of creates or deletes it makes a big difference.
Yup, data=journal will be in the next tests I do.
next prev parent reply other threads:[~2009-11-09 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 9:49 MD performance options: More CPU’s or more Hz’s? mark delfman
2009-11-04 12:08 ` Sujit K M
2009-11-04 12:19 ` mark delfman
2009-11-04 14:05 ` Bill Davidsen
2009-11-04 14:34 ` mark delfman
2009-11-04 15:41 ` jim owens
2009-11-04 15:45 ` jim owens
2009-11-04 15:56 ` jim owens
2009-11-04 17:26 ` mark delfman
2009-11-04 19:09 ` jim owens
2009-11-05 12:34 ` MD performance options: More CPUs or more Hzs? Goswin von Brederlow
2009-11-04 14:39 ` MD performance options: More CPU’s or more Hz’s? John Hughes
2009-11-09 17:24 ` Bill Davidsen
2009-11-09 17:37 ` John Hughes [this message]
2009-11-04 15:01 ` MD performance options: More CPU’s or more Hz’s? Goswin von Brederlow
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=4AF8534C.3030304@Calva.COM \
--to=john@calva.com \
--cc=davidsen@tmr.com \
--cc=linux-raid@vger.kernel.org \
--cc=markdelfman@googlemail.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.