From: Steven Pratt <slpratt@austin.ibm.com>
To: Chris Mason <chris.mason@oracle.com>,
Eric Whitney <eric.whitney@hp.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Updated performance results
Date: Wed, 23 Sep 2009 10:24:42 -0500 [thread overview]
Message-ID: <4ABA3DBA.6000607@austin.ibm.com> (raw)
In-Reply-To: <20090918201409.GF21798@think>
Chris Mason wrote:
> On Thu, Sep 17, 2009 at 05:04:11PM -0500, Steven Pratt wrote:
>
>> Chris Mason wrote:
>>
>>> On Thu, Sep 17, 2009 at 04:17:14PM -0400, Chris Mason wrote:
>>>
>>>> [ crashes on runs involving unmounts ]
>>>>
>>>> The run is still going here, but it has survived longer than before.
>>>> I'm trying with Yan Zheng's patch:
>>>>
>>>> From: Yan Zheng <zheng.yan@oracle.com>
>>>> Date: Fri, 11 Sep 2009 16:11:19 -0400
>>>> Subject: [PATCH] Btrfs: improve async block group caching
>>>>
>>> Quick update, I got through a full run of Steve's test with this
>>> applied. I'll start a few more ;)
>>>
>> Seems to work for me too! Got through all the random write tests
>> with no problems. Will kick off full run overnight.
>>
>
> Thanks again.
>
> I've updated the btrfs-unstable tree to include Yan Zheng's fix. I've
> also included two more buffered writeback speedups, and I expect these
> to make a difference on the multi-threaded tests.
>
> I took a look at 1MB O_DIRECT writes, and the latencies of sending off
> checksumming to the checksum threads seem to be the biggest problem. I
> get full tput at 8MB O_DIRECT writes, so for now I'm going to leave this
> one alone.
>
Updated performance results are available. Ran both the 9/16 tree +
async patches and the tree from 9/18. Results are a mixed bag, some
faster some slower.
http://btrfs.boxacle.net/repository/raid/history/History.html
Steve
> -chris
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2009-09-23 15:24 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
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 [this message]
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=4ABA3DBA.6000607@austin.ibm.com \
--to=slpratt@austin.ibm.com \
--cc=chris.mason@oracle.com \
--cc=eric.whitney@hp.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