From: Roman Mamedov <roman@rm.pp.ru>
To: aragonx@dcsnow.com
Cc: linux-raid@vger.kernel.org
Subject: Re: How to boost performance
Date: Thu, 17 Jun 2010 10:01:09 +0600 [thread overview]
Message-ID: <20100617100109.32a20ffa@natsu> (raw)
In-Reply-To: <ea83c7a1ddca01e0a1535f130502a0f2.squirrel@www.dcsnow.com>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
On Wed, 16 Jun 2010 18:23:36 -0400
aragonx@dcsnow.com wrote:
> Before I start spewing server information, my question is this. Is there
> anything I can tweak to improve my performance? It seems that the server
> is CPU bound when I am transferring large amounts of data to or from it.
> Any suggestions will be considered. Faster processor, switching to RAID
> 0, etc. I'm hoping there is something I can do with the RAID software
> though. Maybe a different chunk size or different algorithm?
Increasing stripe cache size from the default of 256 should help immensely.
echo 16384 > /sys/block/md0/md/stripe_cache_size
Be warned that this consumes (^that amount * 4096 * number of disks) bytes of
RAM. Some benchmarks:
http://peterkieser.com/2009/11/29/raid-mdraid-stripe_cache_size-vs-write-transfer/
On a related note -- Neil, are there plans to implement a stripe cache which
would be shared between all RAID devices? I have two RAID5s in my system, and
when one has a lot of writes, the other is often idle (or vice versa), so that
array's stripe cache is just sitting there wasting memory. Would be nice to
be able to have a shared pool of RAM for stripe-caching all the arrays and
the active one(s) using it to the fullest.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-17 4:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 22:23 How to boost performance aragonx
2010-06-17 4:01 ` Roman Mamedov [this message]
2010-06-17 8:17 ` Michael Evans
2010-06-17 13:49 ` aragonx
2010-06-17 16:13 ` Roman Mamedov
2010-06-17 16:44 ` Stefan /*St0fF*/ Hübner
2010-06-17 19:51 ` aragonx
2010-06-17 22:25 ` Roger Heflin
2010-06-17 19:46 ` aragonx
2010-06-17 19:56 ` aragonx
2010-06-17 20:02 ` Roman Mamedov
2010-06-17 20:43 ` Keld Simonsen
2010-06-18 17:55 ` aragonx
2010-06-18 20:12 ` Roger Heflin
2010-06-20 23:30 ` How to boost performance [SOLVED] aragonx
2010-06-21 0:21 ` Bernd Schubert
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=20100617100109.32a20ffa@natsu \
--to=roman@rm.pp.ru \
--cc=aragonx@dcsnow.com \
--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 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.