From: Chris Mason <chris.mason@oracle.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC PATCH 2/2] Btrfs: introduce free space cluster for each node
Date: Tue, 1 Nov 2011 12:04:40 -0400 [thread overview]
Message-ID: <20111101160440.GA13340@shiny> (raw)
In-Reply-To: <4EAFA21F.5010200@cn.fujitsu.com>
On Tue, Nov 01, 2011 at 03:39:11PM +0800, Miao Xie wrote:
> Any Comment?
This is definitely interesting, in terms of trying to avoid btree
fragmentation and improve the performance of the allocator.
But I'm worried about what happens to performance as the FS fills up?
What kind of benchmarks have you done on larger filesystems that are
almost full?
-chris
next prev parent reply other threads:[~2011-11-01 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 8:18 [RFC PATCH 2/2] Btrfs: introduce free space cluster for each node Miao Xie
2011-11-01 7:39 ` Miao Xie
2011-11-01 16:04 ` Chris Mason [this message]
2011-11-02 2:16 ` Miao Xie
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=20111101160440.GA13340@shiny \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@cn.fujitsu.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).