public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Pratt <slpratt@austin.ibm.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs experimental branch updates
Date: Sun, 15 Mar 2009 09:38:28 -0500	[thread overview]
Message-ID: <49BD12E4.4070505@austin.ibm.com> (raw)
In-Reply-To: <1236994421.17095.7.camel@think.oraclecorp.com>

Chris Mason wrote:
> On Fri, 2009-03-13 at 17:52 -0500, Steven Pratt wrote:
>   
>> Chris Mason wrote:
>>     
>>> Hello everyone,
>>>
>>> I've rebased the experimental branch to include most of the
>>> optimizations I've been working on.
>>>
>>> The two major changes are doing all extent tree operations in delayed
>>> processing queues and removing many of the blocking points with btree
>>> locks held.
>>>
>>> In addition to smoothing out IO performance, these changes really cut
>>> down on the amount of stack btrfs is using, which is especially
>>> important for kernels with 4k stacks enabled (fedora).
>>>
>>>   
>>>       
>> Well, no drastic changes.  On Raid, creates got better, but random write 
>> got worse. Mail server was mixed. For single disk, pretty much the same 
>> story, although CPU savings is noticeable on write, although at the 
>> expense of performance.
>>
>>     
>
> Thanks for running this, but the main performance fixes for your test
> are still in testing locally.  One thing that makes a huge difference on
> the random write run is to mount -o ssd.
>
>   
Tried a run with -o ssd on the raid system. It made some minor 
improvements in random write performance. Helps more on odirect, but 
mainly at the 16thread count. Single and 128 threads it doesn't make 
much difference.

Results syncing now to history boxacle
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
>   


  reply	other threads:[~2009-03-15 14:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 15:56 Btrfs experimental branch updates Chris Mason
2009-03-13 22:52 ` Steven Pratt
2009-03-14  1:33   ` Chris Mason
2009-03-15 14:38     ` Steven Pratt [this message]
2009-03-17  1:24       ` Chris Mason
2009-03-17 20:57         ` Steven Pratt
2009-03-18  1:18           ` Chris Mason
2009-03-15 19:13 ` Grigory Makarevich
2009-03-16 13:31   ` Chris Mason

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=49BD12E4.4070505@austin.ibm.com \
    --to=slpratt@austin.ibm.com \
    --cc=chris.mason@oracle.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