From: Chris Mason <chris.mason@oracle.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Single disk performance
Date: Fri, 26 Jun 2009 16:56:59 -0400 [thread overview]
Message-ID: <20090626205659.GD3951@think> (raw)
In-Reply-To: <4A44DB23.5000400@austin.ibm.com>
On Fri, Jun 26, 2009 at 09:28:51AM -0500, Steven Pratt wrote:
> Upgraded the btrfs tree to 6-17 and all of the stability problems went
> away on the single disk system, so not sure if this was a code problem
> or hardware, but at least stable now.
> Performance results updated at:
> http://btrfs.boxacle.net/repository/single-disk/History/History.html
>
> The fixed to the cow path are obvious for random write, although even on
> single disk the CPU overhead is very noticeable as the efficiency graphs
> show.
>
> The good news is that now the only workload that Btrfs is not at or near
> the top in performance for single disk is MailServer.
Thanks Steve, glad to hear the stability problems are gone.
Could you please try this one liner to see if our big CPU problem during
streaming writes goes away?
diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
index 126477e..7c3cd24 100644
--- a/fs/btrfs/file.c
+++ b/fs/btrfs/file.c
@@ -151,7 +151,10 @@ static noinline int dirty_and_release_pages(struct btrfs_trans_handle *trans,
}
if (end_pos > isize) {
i_size_write(inode, end_pos);
- btrfs_update_inode(trans, root, inode);
+ /* we've only changed i_size in ram, and we haven't updated
+ * the disk i_size. There is no need to log the inode
+ * at this time.
+ */
}
err = btrfs_end_transaction(trans, root);
out_unlock:
next prev parent reply other threads:[~2009-06-26 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 14:28 Single disk performance Steven Pratt
2009-06-26 20:56 ` Chris Mason [this message]
2009-06-27 2:26 ` Steven Pratt
2009-06-29 12:41 ` Chris Mason
2009-06-29 23:17 ` Bron Gondwana
2009-06-30 11:02 ` Chris Mason
2009-06-30 14:38 ` Steven Pratt
2009-06-30 15:10 ` Yan Zheng
2009-06-30 15:26 ` Steven Pratt
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=20090626205659.GD3951@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slpratt@austin.ibm.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