All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: xfs@oss.sgi.com, Eric Sandeen <sandeen@sandeen.net>,
	Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Subject: Re: xfs_growfs / planned resize / performance impact
Date: Sun, 05 Aug 2012 15:26:08 -0500	[thread overview]
Message-ID: <501ED6E0.802@hardwarefreak.com> (raw)
In-Reply-To: <201208051549.22830.Martin@lichtvoll.de>

On 8/5/2012 8:49 AM, Martin Steigerwald wrote:
> Am Sonntag, 5. August 2012 schrieb Stan Hoeppner:
>> On 8/5/2012 6:03 AM, Martin Steigerwald wrote:
>>> Well the default was 16 AGs for volumes < 2 TiB AFAIR. And it has
>>> been reduced to 4 for as I remember exactly performance reasons. Too
>>> many AGs on a single device can incur too much parallelity. Thats at
>>> least is what I have understood back then.
>>
>> For striped md/RAID or LVM volumes mkfs.xfs will create 16 AGs by
>> default because it reads the configuration and finds a striped volume.
>> The theory here is that more AGs offers better performance in the
>> average case on a striped volume.
>>
>> With hardware RAID or a single drive, or any storage configuration for
>> which mkfs.xfs is unable to query the parameters, mkfs.xfs creates 4
>> AGs by default.  The 4 AG default has been with us for a very long
>> time.  It was never reduced.
> 
> That does not match my memory, but I´d have to look it up. Maybe next 
> week.
> 
> I am pretty sure mkfs.xfs on a single partition on a single harddisk upto 
> 2 TiB used 16 AGs for quite some time and now uses 4 AGs since quite some 
> time already. I think I have noted the exact xfsprogs version where it was 
> changed in my training slides.

>From 'man mkfs.xfs' of xfsprogs 3.1.4 (probably not the latest)

"The data section of the filesystem is divided into _value_ allocation
groups (default value is scaled automatically based on the underlying
device size)."

It's not stated in man but the minimum is 4 AGs, unless that has changed
in the last couple of years.  This is what I was referring to previously
when I stated 4 AGs is the default.

What you likely did was format a 2TB device and saw 16 AGs due to the
automatic scaling, then shortly thereafter formatted a much smaller
device and saw the default minimum 4 AGs.  Assuming agcount was
statically defined, you assumed the default value had been decreased.

-- 
Stan

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

  reply	other threads:[~2012-08-05 20:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 13:56 xfs_growfs / planned resize / performance impact Stefan Priebe - Profihost AG
2012-07-31 17:27 ` Stan Hoeppner
2012-08-03  4:03 ` Eric Sandeen
2012-08-03  6:09   ` Stefan Priebe - Profihost AG
2012-08-03 13:46     ` Eric Sandeen
2012-08-05 11:03     ` Martin Steigerwald
2012-08-05 12:34       ` Stan Hoeppner
2012-08-05 13:49         ` Martin Steigerwald
2012-08-05 20:26           ` Stan Hoeppner [this message]
2012-08-05 15:54       ` Stefan Priebe
2012-08-06 11:42         ` Michael Monnerie
2012-08-04 22:43 ` Dave Chinner
2012-08-05  5:46   ` Stefan Priebe
2012-08-05 11:06     ` Martin Steigerwald
2012-08-05 11:35     ` Andy Bennett
2012-08-05 20:57     ` 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=501ED6E0.802@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=Martin@lichtvoll.de \
    --cc=s.priebe@profihost.ag \
    --cc=sandeen@sandeen.net \
    --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 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.