From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Cc: Stan Hoeppner <stan@hardwarefreak.com>
Subject: Re: XFS journaling position
Date: Fri, 29 Oct 2010 09:58:02 +0200 [thread overview]
Message-ID: <201010290958.03513@zmi.at> (raw)
In-Reply-To: <4CCA0834.8040703@hardwarefreak.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 2706 bytes --]
On Freitag, 29. Oktober 2010 Stan Hoeppner wrote:
> So as we move to a totally virtualized guest OS, we then lose the
> stripe width and stripe size information. How much performance does
> this really cost us WRT XFS filesystem layout?
This is still a very straightforward config. When you use a NetApp
storage with virtualization, you normally use thin provisioning. So you
put one VM with it's root FS on that system, and assign a data disk of
1.4TB. You then "flexclone" that VM 9 times, so you have 10 VMs running
but they only use the diskspace of one. Then you upgrade or modify one
VM, and only the blocks that are modified get copied on the disks.
You fill 5 VMs in parallel with data, and it gets stored totally
"fragmented" on the storage. Now do a snapshot of a VM, so it's old
contents are frozen and every write gets written to a new place.
There are companies who do a snapshot of every VM every hour, so their
users can by themself recover files that they deleted/modifed wrongly.
And now take into account that NetApp uses WAFL - write anywhere file
layout. It means that even if you have a VM straight on disk, as soon as
you modify a block it can be written in a totally different place on the
storage.
I'd say this is such a "total mess" where you know exactly *nothing*
about the layout of anything. You cannot even optimize for stripe size.
> How many folks are running their
> critical core business databases in virtual machine guests? How
> about core email systems? Other performance/business critical
> applications?
I don't know which country you are from, I'm from Austria/Europe (not
the kangaroo country :-). On every single tech talk and presentation I
visited this year, every single speaker talked about virtualization.
Depending on who spoke, either 2009 or 2010 were the years where more
virtual servers were deployed than physical ones, with a sharp increase
each year. We didn't sell a single server running bare-metal OS, all had
VMware or XenServer.
And for business critical: SAP uses virtualization everywhere in-house,
ÖBB (Austrian Railways) use Xen for virtualized central accounting
program since 2001 exclusively. These are just the 2 companies who were
speaking on last weeks presentation, there are far more.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Radiointerview zum Thema Spam ******
http://www.it-podcast.at/archiv.html#podcast-100716
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-10-29 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 5:26 XFS journaling position klonatos
2010-10-25 16:10 ` Geoffrey Wehrman
2010-10-26 22:27 ` Michael Monnerie
2010-10-26 23:28 ` Dave Chinner
2010-10-26 23:59 ` Michael Monnerie
2010-10-27 14:27 ` Robert Brockway
2010-10-27 14:32 ` Robert Brockway
2010-10-28 9:44 ` Michael Monnerie
2010-10-28 23:33 ` Stan Hoeppner
2010-10-29 7:58 ` Michael Monnerie [this message]
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=201010290958.03513@zmi.at \
--to=michael.monnerie@is.it-management.at \
--cc=stan@hardwarefreak.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