public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Carlos Maiolino <cmaiolino@redhat.com>
To: xfs@oss.sgi.com, linux-xfs@oss.sgi.com
Subject: Re: ag selection
Date: Mon, 11 Nov 2013 15:53:14 -0200	[thread overview]
Message-ID: <20131111175313.GA16643@orion.maiolino.org> (raw)
In-Reply-To: <l5r3tf$m0j$1@ger.gmane.org>

On Mon, Nov 11, 2013 at 06:25:13PM +0100, Bernd Schubert wrote:
> Hi all,
> 
> for streaming writes onto a raid6 the current round-robin ag
> selection seems does not seem to be optimal. Writing 4 files from 4
> threads into a single directory we get 900 MB/s, writing 4 files in
> 4 different directories we only get 700 MB/s (12 disks with with hw
> megaraid-sas). The current round-robin scheme seems to be optimized
> for linear raid0? With small AGs one could also argue, that choosing
> AGs which are not far away from each other (in respect to the number
> of blocks) also adds more parallel disk access for small and medium
> sized files.
> 
> Any objections against a patch to improve the AG selection?
> 

I wouldn't say this it is optimized specifically for raid 0 environments but I
lack some knowledge on this choice. The mainly reason for the round-robing IIRC,
was to avoid lock contention in a single AG. spreading different files along the
whole disk, and also making it able to allocate them contiguously along the disk.

But, I'm not sure what kind of optimization you have in mind and I believe
another engineers will also need some extra information about what optimization
you have in mind, what kind of tests you're doing (Direct I/O, buffered,
pre-allocation), etc.. You'll also need to post filesystem configurations like
FS aligment (su, sw options), etc.

For different write patterns, you might also want to take a look at the
rotor_step procfs option, and some other options dedicated to streaming writes,
that might help you in this case.

Just my $0.02

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

-- 
Carlos

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

  reply	other threads:[~2013-11-11 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 17:25 ag selection Bernd Schubert
2013-11-11 17:53 ` Carlos Maiolino [this message]
2013-11-11 17:55   ` Carlos Maiolino
2013-11-11 18:23     ` Bernd Schubert
2013-11-11 18:30       ` Eric Sandeen
2013-11-11 19:42         ` Bernd Schubert
2013-11-11 20:55 ` Dave Chinner

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=20131111175313.GA16643@orion.maiolino.org \
    --to=cmaiolino@redhat.com \
    --cc=linux-xfs@oss.sgi.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