From: Chris Mason <chris.mason@oracle.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: New experimental btrfs branch ready for testing
Date: Tue, 9 Jun 2009 11:26:39 -0400 [thread overview]
Message-ID: <20090609152639.GB9556@think> (raw)
In-Reply-To: <4A2A9B95.5050604@austin.ibm.com>
On Sat, Jun 06, 2009 at 11:38:45AM -0500, Steven Pratt wrote:
>
> No problem. Raid results are uploading to
> http://btrfs.boxacle.net/repository/raid/history/History.html now.
> There were massive improvements in the random write workloads,
> especially with cow enabled!! MailServer had moderate perf gains, but
> dramatic decrease in CPU utilization, so this is very good as well.
>
> The only regression I see is on large file creates, CPU is up 200% or
> more while performance is fairly flat. btrfs_tree_lock now dominates
> the profile.
I'm not able to reproduce the btrfs_tree_lock usage that you're seeing.
Could you please use the callgraph option to oprofile?
-chris
next prev parent reply other threads:[~2009-06-09 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 21:04 New experimental btrfs branch ready for testing Chris Mason
2009-06-02 13:28 ` Chris Mason
2009-06-03 17:08 ` Chris Mason
2009-06-04 19:02 ` Steven Pratt
2009-06-04 19:05 ` Chris Mason
2009-06-05 14:20 ` Chris Mason
2009-06-05 16:02 ` Steven Pratt
2009-06-05 21:27 ` Steven Pratt
2009-06-06 0:20 ` Chris Mason
2009-06-06 16:38 ` Steven Pratt
2009-06-09 15:26 ` Chris Mason [this message]
2009-06-15 15:46 ` Steven Pratt
2009-06-07 11:50 ` Roy Sigurd Karlsbakk
2009-06-07 12:13 ` Daniel Cordero
2009-06-08 12:33 ` Yan Zheng
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=20090609152639.GB9556@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 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.