From: Alexander Graf <agraf@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, hch@lst.de
Subject: Re: [Qemu-devel] Re: [PATCH] Add cache=volatile parameter to -drive
Date: Mon, 17 May 2010 16:22:54 +0200 [thread overview]
Message-ID: <4BF1513E.40408@suse.de> (raw)
In-Reply-To: <4BF14CE9.5040907@suse.de>
Alexander Graf wrote:
> Anthony Liguori wrote:
>
>> On 05/17/2010 08:17 AM, Alexander Graf wrote:
>>
>>> On 17.05.2010, at 15:09, Anthony Liguori wrote:
>>>
>>>
>>>
>>>> On 05/17/2010 08:02 AM, Alexander Graf wrote:
>>>>
>>>>
>>>>>> My concern is that ext3 exaggerates the cost of fsync() which will
>>>>>> result in diminishing value over time for this feature as people
>>>>>> move to ext4/btrfs.
>>>>>>
>>>>>>
>>>>>>
>>>>> There will be ext3 file systems for years out. Just because people
>>>>> can use better and faster file systems doesn't mean they do. And
>>>>> I'm sure they can't always choose. If anything, I can try and see
>>>>> what the numbers look like for xfs.
>>>>>
>>>>>
>>>>>
>>>> But ext3 with barrier=1 is pretty uncommon in practice. Another
>>>> data point would be an ext3 host file system with barrier=0.
>>>>
>>>>
>>> Who defines what is common and what not? To me, the SLES11 default is
>>> common. In fact, the numbers in the referred mail were done on an
>>> 11.1 system.
>>>
>>>
>> But it wasn't the SLES10 default so there's a smaller window of
>> systems that are going to be configured this way. But this is
>> orthogonal to the main point. Let's quantify how important this
>> detail is before we discuss the affected user base.
>>
>
> Alright. I took my Netbook (2GB of RAM) and a USB hard disk, so I can
> easily remount the data fs the vmdk image is on. Here are the results:
>
> # mkfs.ext3 /dev/sdc1
> # mount /dev/sdc1 /mnt -obarrier=1
>
> cache=writeback
>
> real 0m52.801s
> user 0m16.065s
> sys 0m6.688s
>
> cache=volatile
>
> real 0m47.876s
> user 0m15.921s
> sys 0m6.548s
>
> # mount /dev/sdc1 /mnt -obarrier=0
>
> cache=writeback
>
> real 0m53.588s
> user 0m15.901s
> sys 0m6.576s
>
> cache=volatile
>
> real 0m48.715s
> user 0m16.581s
> sys 0m5.856s
>
> I don't see a difference between the results. Apparently the barrier
> option doesn't change a thing.
>
The same test case for XFS:
cache=writeback
real 0m50.868s
user 0m11.133s
sys 0m12.733s
cache=volatile
real 0m43.680s
user 0m16.089s
sys 0m7.812s
Though I did have numbers here going as far down as 25 seconds for a run!
Alex
next prev parent reply other threads:[~2010-05-17 14:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 10:14 [Qemu-devel] [PATCH] Add cache=volatile parameter to -drive Alexander Graf
2010-05-17 10:42 ` [Qemu-devel] " Kevin Wolf
2010-05-17 12:58 ` Anthony Liguori
2010-05-17 13:02 ` Alexander Graf
2010-05-17 13:09 ` Anthony Liguori
2010-05-17 13:17 ` Alexander Graf
2010-05-17 13:26 ` Anthony Liguori
2010-05-17 14:04 ` Alexander Graf
2010-05-17 14:22 ` Alexander Graf [this message]
2010-05-17 15:16 ` Anthony Liguori
2010-05-17 16:23 ` Paul Brook
2010-05-17 16:26 ` Anthony Liguori
2010-05-17 16:28 ` Alexander Graf
2010-05-17 20:07 ` Jamie Lokier
2010-05-18 7:42 ` Kevin Wolf
2010-05-25 17:59 ` Alexander Graf
2010-05-25 18:48 ` Anthony Liguori
2010-05-25 19:01 ` Alexander Graf
2010-05-26 13:09 ` Avi Kivity
2010-05-25 21:01 ` Aurelien Jarno
2010-05-26 1:31 ` Anthony Liguori
2010-05-26 8:43 ` Kevin Wolf
2010-05-26 13:42 ` Anthony Liguori
2010-05-26 14:03 ` Kevin Wolf
2010-05-26 14:08 ` Anthony Liguori
2010-05-26 14:26 ` Kevin Wolf
2010-05-26 14:13 ` Aurelien Jarno
2010-05-26 8:52 ` Aurelien Jarno
2010-05-26 9:16 ` Kevin Wolf
2010-05-26 13:48 ` Anthony Liguori
2010-05-26 14:12 ` Aurelien Jarno
2010-05-26 14:19 ` Anthony Liguori
2010-05-26 15:40 ` Aurelien Jarno
2010-05-26 16:11 ` Anthony Liguori
2010-05-26 14:27 ` Paolo Bonzini
2010-05-26 13:06 ` Avi Kivity
2010-05-26 13:50 ` Anthony Liguori
2010-05-26 15:13 ` Avi Kivity
2010-05-17 15:11 ` Anthony Liguori
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=4BF1513E.40408@suse.de \
--to=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.