linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Chris Mason <chris.mason@oracle.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: the idea for improving the performance of b-tree search
Date: Mon, 18 Oct 2010 17:36:30 +0800	[thread overview]
Message-ID: <4CBC151E.3070705@cn.fujitsu.com> (raw)
In-Reply-To: <20101018024141.GA5416@sli10-conroe.sh.intel.com>

On Mon, 18 Oct 2010 10:41:41 +0800, Shaohua Li wrote:
> Hi Miao&  Chris,
> On Wed, Oct 13, 2010 at 05:00:56PM +0800, Miao Xie wrote:
>> When I investigated the performance problem of file creation/deletion, I found
>> btrfs spends lots of time in the b-tree search, so I consider whether we can use
>> the latest search result in the same transaction or not.
>>
>> My idea follows:
>> we can add mask or time stamp into b-tree's node and leaf, then we know whether
>> the node/leaf is COWed by the other task. If not, we check if the node/leaf of
>> the latest search result contains the key that we want to search. By this way,
>> we can reuse the latest search result in the same transaction and reduce the CPU
>> time spent in the b-tree search.
> Does this patch help a little for the tree search?
> http://marc.info/?l=linux-btrfs&m=127175532803943&w=2
> It doesn't solve all the issues, but in my test, it does help.

Thanks for your patch, but according to my test result, the time of b-tree search
has not been reduced. I think the reason is that extent-state is used when btrfs writes
data into the disk, so your patch is helpful when the disk I/O happens, but my test just
measures the cost of the b-tree searchs/insertions/removals, the disk I/O doesn't happen.

Regards
Miao

      reply	other threads:[~2010-10-18  9:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13  9:00 the idea for improving the performance of b-tree search Miao Xie
2010-10-13 11:24 ` Chris Mason
2010-10-13 15:22   ` David Nicol
2010-10-13 15:45     ` Chris Mason
2010-10-13 20:38       ` David Nicol
2010-10-18  2:41 ` Shaohua Li
2010-10-18  9:36   ` Miao Xie [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=4CBC151E.3070705@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=shaohua.li@intel.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;
as well as URLs for NNTP newsgroup(s).