From: aragonx@dcsnow.com
To: Roman Mamedov <roman@rm.pp.ru>
Cc: aragonx@dcsnow.com, linux-raid@vger.kernel.org
Subject: Re: How to boost performance
Date: Thu, 17 Jun 2010 09:49:42 -0400 [thread overview]
Message-ID: <d98b7022efc6988e47f7e4114aa83f62.squirrel@www.dcsnow.com> (raw)
In-Reply-To: <20100617100109.32a20ffa@natsu>
> On Wed, 16 Jun 2010 18:23:36 -0400
> 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:
Hello. Thank you for the quick suggestions!
First I need to correct myself. I only have the slowdown when writing to
the server. Reads from the server are usually in the 60-70MB/sec range
regardless of file size.
Prior to the change above, on a 2GB file, I would start off the write (to
the server) at 70MB/sec and end at about 35MB/sec. CPU usage was at 100%
with the md0 using about 70% CPU and smb using 30% with flush sometimes
jumping in at 30%. Wait states remained below 10%. After the change, on
a 2GB file I would start the write at 70MB/sec and end about 55MB/sec
(nice improvement!).
Switched to a 5GB file and the write ended around 35MB/sec. At the
beginning smbd would star with 50% CPU but gradually go down to 30% with
md0 ramping up to 70% and flush jumping in from time to time at 30%.
This information is all coming from top. If I should use something else
that will get more accurate readings, please let me know.
With one change my performance greatly increased but I would like to see
more. Is there anything else I can do? I'm hoping to get sustainable
60MB/sec writes. Is that possible?
Thank you if you have read this far! :)
---
Will Y.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2010-06-17 13:49 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
2010-06-17 8:17 ` Michael Evans
2010-06-17 13:49 ` aragonx [this message]
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=d98b7022efc6988e47f7e4114aa83f62.squirrel@www.dcsnow.com \
--to=aragonx@dcsnow.com \
--cc=linux-raid@vger.kernel.org \
--cc=roman@rm.pp.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).