From: Ben Gamari <bgamari.foss@gmail.com>
To: Avi Kivity <avi@redhat.com>, linux-btrfs@vger.kernel.org
Cc: Andi Kleen <andi@firstfloor.org>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, tytso@mit.edu, npiggin@suse.de,
mingo@elte.hu, Ruald Andreae <ruald.a@gmail.com>,
Jens Axboe <jens.axboe@oracle.com>, Olly Betts <olly@survex.com>,
martin f krafft <madduck@madduck.net>
Subject: Re: Poor interactive performance with I/O loads with fsync()ing
Date: Sun, 11 Apr 2010 09:35:37 -0700 (PDT) [thread overview]
Message-ID: <4bc1fa59.c5c2f10a.776d.ffffcd91@mx.google.com> (raw)
In-Reply-To: <4BC1E4A4.1070103@redhat.com>
On Sun, 11 Apr 2010 18:03:00 +0300, Avi Kivity <avi@redhat.com> wrote:
> On 04/09/2010 05:56 PM, Ben Gamari wrote:
> > On Mon, 29 Mar 2010 00:08:58 +0200, Andi Kleen<andi@firstfloor.org> wrote:
> >
> >> Ben Gamari<bgamari.foss@gmail.com> writes:
> >> ext4/XFS/JFS/btrfs should be better in this regard
> >>
> >>
> > I am using btrfs, so yes, I was expecting things to be better. Unfortunately,
> > the improvement seems to be non-existent under high IO/fsync load.
> >
>
> btrfs is known to perform poorly under fsync.
>
Has the reason for this been identified? Judging from the nature of metadata
loads, it would seem that it should be substantially easier to implement
fsync() efficiently.
- Ben
next parent reply other threads:[~2010-04-11 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4b9fa440.12135e0a.7fc8.ffffe745@mx.google.com>
[not found] ` <4baeaee5.c5c2f10a.7187.2688@mx.google.com>
[not found] ` <20100327204233.0d84542a@infradead.org>
[not found] ` <4baf624c.48c3f10a.16d0.ffffccb8@mx.google.com>
[not found] ` <87y6hcyu85.fsf@basil.nowhere.org>
[not found] ` <4bbf401e.a3b9e70a.13f3.4460@mx.google.com>
[not found] ` <4BC1E4A4.1070103@redhat.com>
2010-04-11 16:35 ` Ben Gamari [this message]
2010-04-11 17:20 ` Poor interactive performance with I/O loads with fsync()ing Andi Kleen
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=4bc1fa59.c5c2f10a.776d.ffffcd91@mx.google.com \
--to=bgamari.foss@gmail.com \
--cc=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=avi@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madduck@madduck.net \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=olly@survex.com \
--cc=ruald.a@gmail.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).