public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: pg_xfs2@xfs2.for.sabi.co.UK (Peter Grandi)
To: Linux XFS <xfs@oss.sgi.com>
Subject: Re: Poor VMWare disk performance on XFS partition
Date: Mon, 24 Mar 2008 15:24:46 +0000	[thread overview]
Message-ID: <18407.51134.786769.234995@tree.ty.sabi.co.uk> (raw)
In-Reply-To: <47E7B3E4.1020205@thebarn.com>

>>> On Mon, 24 Mar 2008 09:00:04 -0500, Russell Cattelan
>>> <cattelan@thebarn.com> said:

>> [ ... ] Mount XFS partition with "nobarrier" option. [ ... ]

> I can verify that ... barriers are killers when running vmware
> guest disk/memory images. [ ... ]

But of course running VM images with 'nobarrier' is quite brave:
because it removes *any* integrity guarantee to IO initiated
inside the virtual machine.

This is because the only safe behaviour for a virtual machine
software is to turn all VM storage operations into synchronous
ones (or else detect the use of barriers inside the virtual
machine).

Of course this is going to be catastrophic with XFS's delayed
allocations, which relies on large numbers of outstanding writes
to coalesce them into large segments.

> [ ... ] The preallocation would also help out quite bit if you
> don't mind dedicating the disk space vs the sparse file method,
> which allow for over subscribing the physical space. [ ... ]

But sparse files are a crazy idea for virtual machines, because
the software inside is built on the idea that its storage is
allocated in contiguous volumes, and relies on that for its own
optimizations.

Or else one ends up with a CP/CMS situation where the "CMS"
inside the virtual machine is fully aware that it is running
inside a virtual machine and passes "out-of-bandwidth" hints to
the virtual machine software.

  reply	other threads:[~2008-03-24 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 14:50 Poor VMWare disk performance on XFS partition Hendrik .
2008-03-23 20:42 ` Eric Sandeen
2008-03-24  4:02   ` Andi Kleen
2008-03-24  0:41 ` Jan Derfinak
2008-03-24 14:00   ` Russell Cattelan
2008-03-24 15:24     ` Peter Grandi [this message]
2008-03-24 18:56       ` Jan Derfinak
2008-03-24 19:12       ` Josef 'Jeff' Sipek

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=18407.51134.786769.234995@tree.ty.sabi.co.uk \
    --to=pg_xfs2@xfs2.for.sabi.co.uk \
    --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