From: Wolfgang Denk <wd@denx.de>
To: linux-raid@vger.kernel.org
Subject: Optimize RAID0 for max IOPS?
Date: Tue, 18 Jan 2011 22:01:12 +0100 [thread overview]
Message-ID: <20110118210112.D13A236C@gemini.denx.de> (raw)
Hi,
I'm going to replace a h/w based RAID system (3ware 9650SE) by a plain
s/w RAID0, because the existing system appears to be seriously limited
in terms of numbers of I/O operations per second.
Our workload is mixed read / write (something between 80% read / 20%
write and 50% / 50%), consisting of a very large number of usually
very small files.
There may be 20...50 millions of files, or more. 65% of the files are
smaller than 4 kB; 80% are smaller than 8 kB; 90% are smaller than 16
kB; 98.4% are smaller than 64 kB.
I will have 4 x 1 TB disks for this setup.
The plan is to build a RAID0 from the 4 devices, create a physical
volume and a volume group on the resulting /dev/md?, then create 2 or
3 logical volumes that will be used as XFS file systems.
My goal is to optimize for maximum number of I/O operations per
second. [I am aware that using SSDs would be a nice thing, but that
would be too expensive.]
Is this a reasonable approach for such a task?
Should I do anything different to acchive maximum performance?
What are the tunables in this setup? [It seems the usual recipies are
more oriented in maximizing the data troughput for large, mostly
sequential accesses - I figure that things like increasing read-ahead
etc. will not help me much here?]
Thanks in advance.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Quote from a recent meeting: "We are going to continue having these
meetings everyday until I find out why no work is getting done."
next reply other threads:[~2011-01-18 21:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 21:01 Wolfgang Denk [this message]
2011-01-18 22:18 ` Optimize RAID0 for max IOPS? Roberto Spadim
2011-01-19 7:04 ` Wolfgang Denk
2011-01-18 23:15 ` Stefan /*St0fF*/ Hübner
2011-01-19 0:05 ` Roberto Spadim
2011-01-19 7:11 ` Wolfgang Denk
2011-01-19 8:18 ` Stefan /*St0fF*/ Hübner
2011-01-19 8:29 ` Jaap Crezee
2011-01-19 9:32 ` Jan Kasprzak
2011-01-19 7:10 ` Wolfgang Denk
2011-01-19 19:21 ` Wolfgang Denk
2011-01-19 19:50 ` Roberto Spadim
2011-01-19 22:36 ` Stefan /*St0fF*/ Hübner
2011-01-19 23:09 ` Roberto Spadim
2011-01-19 23:18 ` Roberto Spadim
2011-01-20 2:48 ` Keld Jørn Simonsen
2011-01-20 3:53 ` Roberto Spadim
2011-01-21 19:34 ` Wolfgang Denk
2011-01-21 20:03 ` Roberto Spadim
2011-01-21 20:04 ` Roberto Spadim
2011-01-24 14:40 ` CoolCold
2011-01-24 15:25 ` Justin Piszcz
2011-01-24 20:48 ` Wolfgang Denk
2011-01-24 21:57 ` Wolfgang Denk
2011-01-24 23:03 ` Dave Chinner
2011-01-25 7:39 ` Emmanuel Florac
2011-01-25 8:36 ` Dave Chinner
2011-01-25 12:45 ` Wolfgang Denk
2011-01-25 12:51 ` Emmanuel Florac
2011-01-24 20:43 ` Wolfgang Denk
2011-01-25 17:10 ` Christoph Hellwig
2011-01-25 18:41 ` Wolfgang Denk
2011-01-25 21:35 ` Christoph Hellwig
2011-01-26 7:16 ` Wolfgang Denk
2011-01-26 8:32 ` Stan Hoeppner
2011-01-26 8:42 ` Wolfgang Denk
2011-01-26 9:38 ` Christoph Hellwig
2011-01-26 9:41 ` CoolCold
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=20110118210112.D13A236C@gemini.denx.de \
--to=wd@denx.de \
--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).