public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: John Bokma <contact@johnbokma.com>
Cc: xfs@oss.sgi.com
Subject: Re: 30 TB RAID6 + XFS slow write performance
Date: Mon, 18 Jul 2011 19:00:18 -0500	[thread overview]
Message-ID: <4E24C912.20003@sandeen.net> (raw)
In-Reply-To: <4E24907F.6020903@johnbokma.com>

On 7/18/11 2:58 PM, John Bokma wrote:
> Dear list members,
> 
> A customer of mine is currently struggling with the performance of a
> 30 TB RAID6 which uses XFS as the filing system. I am somewhat sure
> it's not XFS that's causing the performance issue but my expertise is
> not XFS nor RAID; I just wrote the software that after moving to the
> larger RAID (from a much smaller one, ~ 3TB, using ext3) suddenly
> seems to have a huge drop in write performance.
> 
> The software I wrote writes many small (50-150K) files in parallel
> (100+ processes), thousands of times per hour. Writing a file of
> 50-150K now and then seems to take between 30 and 90 seconds, and
> more rarely can take over 200 seconds (several times an hour).
> 
> When all processes are stopped and restarted again the 30-90 seconds
> delay start happening when about 16-20+ processes are running.
> 
> To me this sounds like something has been configured wrong. I already
> recommended my customer to find someone who is capable of configuring
> the RAID correctly; to me it sounds like a hardware/configuration
> issue.
> 
> Any insights are very welcome.
> 
> Hardware: card: MegaRAID SAS 9260-16i disks: 14x Barracuda® XT
> ST33000651AS 3TB (2 hot spares). RAID6 ~ 30TB

My first suggestion would be to check the partition alignment on the raid (if it is partitioned), and be sure it is aligned with the underlying raid geometry.

And then make sure you give mkfs.xfs the proper geometry as well.

After that, does the raid card have a battery-backed write cache?  If so, you can safely disable barriers.

More info is always good too, for starters what kernel & what xfsprogs version?

What mkfs & mount options?

-Eric

> Thanks for reading, John
> 
> _______________________________________________ xfs mailing list 
> xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-07-19  0:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 19:58 30 TB RAID6 + XFS slow write performance John Bokma
2011-07-19  0:00 ` Eric Sandeen [this message]
2011-07-19  8:37 ` Emmanuel Florac
2011-07-19 22:37   ` Stan Hoeppner
2011-07-20  0:20     ` Dave Chinner
2011-07-20  5:16       ` Stan Hoeppner
2011-07-20  6:44         ` Dave Chinner
2011-07-20 12:10           ` Stan Hoeppner
2011-07-20 14:04             ` Michael Monnerie
2011-07-20 23:01               ` Dave Chinner
2011-07-21  6:19                 ` Michael Monnerie
2011-07-21  6:48                   ` Dave Chinner
2011-07-22  6:10                     ` Michael Monnerie
2011-07-22 18:05                       ` Stan Hoeppner
2011-07-22 23:10                         ` Dave Chinner
2011-07-24  6:14                           ` Stan Hoeppner
2011-07-24  8:47                             ` Michael Monnerie

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=4E24C912.20003@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=contact@johnbokma.com \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox