linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@fusionio.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: turbo charge fsync
Date: Fri, 24 Aug 2012 14:42:08 -0400	[thread overview]
Message-ID: <20120824184208.GA22819@shiny> (raw)
In-Reply-To: <1345833808-1539-1-git-send-email-jbacik@fusionio.com>

On Fri, Aug 24, 2012 at 12:43:28PM -0600, Josef Bacik wrote:
> 
>                 Original        Patched
> SATA drive      82KB/s          140KB/s
> Fusion drive    431KB/s         2532KB/s
> 
> So around 2-6 times faster depending on your hardware.  There are a few
> corner cases, for example if you truncate at all we have to do it the old
> way since there is no way to be sure what is in the log is ok.  This
> probably could be done smarter, but if you write-fsync-truncate-write-fsync
> you deserve what you get.  All this work is in RAM of course so if your
> inode gets evicted from cache and you read it in and fsync it we'll do it
> the slow way if we are still in the same transaction that we last modified
> the inode in.

I think I sent Liubo down the wrong path on this one, and Josef and I
banged out some ideas for a different (hopefully less complex) way to
solve the problem.  Josef, these results look fantastic.

-chris

  reply	other threads:[~2012-08-24 18:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 18:43 [PATCH] Btrfs: turbo charge fsync Josef Bacik
2012-08-24 18:42 ` Chris Mason [this message]
2012-08-25  3:21   ` Liu Bo

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=20120824184208.GA22819@shiny \
    --to=chris.mason@fusionio.com \
    --cc=jbacik@fusionio.com \
    --cc=linux-btrfs@vger.kernel.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 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).