From: Eric Whitney <eric.whitney@hp.com>
To: Chris Mason <chris.mason@oracle.com>,
Steven Pratt <slpratt@austin.ibm.com>,
Eric Whitney <eric.whitney@hp.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Updated performance results
Date: Thu, 17 Sep 2009 14:32:13 -0400 [thread overview]
Message-ID: <4AB280AD.5080306@hp.com> (raw)
In-Reply-To: <20090916005225.GG23965@think>
Chris Mason wrote:
> On Mon, Sep 14, 2009 at 04:41:48PM -0500, Steven Pratt wrote:
>> Only bit of bad news is I did get one error that crashed the system
>> on single threaded nocow run. So that data point is missing.
>> Output below:
>
> I hope I've got this fixed. If you pull from the master branch of
> btrfs-unstable there are fixes for async thread races. The single
> patch I sent before is included, but not enough.
Chris:
FYI - all five of my test systems have now finished my standard test
cycle on the -unstable master branch, and I've not seen a single hang.
So, your fix for the async thread shutdown race seems to have fixed my
problems, even if Steve's still seeing trouble.
I'll note that the running times for fsstress on some of my systems have
become rather longer with btrfs-unstable/master kernels - 3.5 rather
than 2.5 hours on multidevice filesystems. Running times on single
device filesystems are roughly the same.
I'm going to start another set of tests for thoroughness unless you've
got more patches coming.
Thanks,
Eric
>
> -chris
>
next prev parent reply other threads:[~2009-09-17 18:32 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 18:35 Updated performance results Steven Pratt
2009-07-23 21:00 ` Chris Mason
2009-07-23 22:04 ` Steven Pratt
2009-07-24 13:24 ` Chris Mason
2009-07-24 14:00 ` Chris Mason
2009-07-24 15:05 ` Steven Pratt
2009-07-28 20:12 ` Steven Pratt
2009-07-28 20:23 ` Chris Mason
2009-07-28 21:10 ` Steven Pratt
2009-08-05 20:35 ` Chris Mason
2009-08-07 7:30 ` debian developer
2009-08-07 13:56 ` Steven Pratt
2009-08-07 13:56 ` Steven Pratt
2009-08-07 23:12 ` Chris Mason
2009-08-31 17:49 ` Steven Pratt
2009-09-11 19:29 ` Chris Mason
2009-09-11 21:35 ` Steven Pratt
2009-09-14 13:51 ` Chris Mason
2009-09-14 17:20 ` Jens Axboe
2009-09-14 21:41 ` Steven Pratt
2009-09-14 23:13 ` Chris Mason
2009-09-16 0:52 ` Chris Mason
2009-09-16 15:15 ` Steven Pratt
2009-09-16 17:57 ` Steven Pratt
2009-09-16 18:07 ` Chris Mason
2009-09-16 18:15 ` Steven Pratt
2009-09-16 18:17 ` Chris Mason
2009-09-16 18:16 ` Steven Pratt
2009-09-16 18:20 ` Chris Mason
2009-09-16 18:37 ` Steven Pratt
2009-09-17 18:32 ` Eric Whitney [this message]
2009-09-17 18:39 ` Steven Pratt
2009-09-17 18:52 ` Chris Mason
2009-09-17 20:17 ` Chris Mason
2009-09-17 20:43 ` Chris Mason
2009-09-17 22:04 ` Steven Pratt
2009-09-18 20:14 ` Chris Mason
2009-09-23 15:24 ` 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=4AB280AD.5080306@hp.com \
--to=eric.whitney@hp.com \
--cc=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.