From: Andy Bennett <andyjpb@ashurst.eu.org>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs_growfs / planned resize / performance impact
Date: Sun, 05 Aug 2012 12:35:30 +0100 [thread overview]
Message-ID: <501E5A82.1020909@ashurst.eu.org> (raw)
In-Reply-To: <C4E0639A-87DE-4D38-8097-9B71D0947ABE@profihost.ag>
Hi,
>>> Is it a problem if this grow will happen in small portions (30GB =>
>>> 50GB => 75GB => 100GB => ... 300GB)?
>>
>> Growing a filesystem by an order of magnitude is the limit of what
>> I'd suggest is sane. Growing it by two orders of magnitude
>> (espcially if you start with a 16 AG filesystem because of stripe
>> alignment) is going to cause problems with the number of AGs and
>> the subsequent freespace management scale issue....
> I would start with ag=4 and end up in ag 48 in my tests.
>
>> Growing it by two orders of magnitude
> what does that mean? (sorry no native speaker)
In base 10 an order of magnitude is 10x. Two orders of magnitude would
be 100x.
Numbers of the same order of magnitude have the decimal point (comma in
EU) in the same place.
300GB is an order of magnitude larger than 30GB.
Sometimes, I've seen computer scientists use binary orders of magnitude.
I.e. 2x, 4x, 8x, 16x. I'm not sure if this is generally accepted or not.
Regards,
@ndy
--
andyjpb@ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-08-05 11:35 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
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 [this message]
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=501E5A82.1020909@ashurst.eu.org \
--to=andyjpb@ashurst.eu.org \
--cc=s.priebe@profihost.ag \
--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