From: Zach Brown <zab@zabbo.net>
To: Josef Bacik <josef@redhat.com>
Cc: Danny Piccirillo <danny.piccirillo@member.fsf.org>,
linux-btrfs@vger.kernel.org
Subject: Re: Fractal Tree Indexing over B-Trees?
Date: Wed, 28 Mar 2012 15:50:07 -0400 [thread overview]
Message-ID: <4F736B6F.2080805@zabbo.net> (raw)
In-Reply-To: <20120328185720.GC1941@localhost.localdomain>
> but lets say O(log N/2) where N is the number of elements in the row.
> So in the situation I describe you are looking at having to do minimum
> of 29 reads, one for each row,
Hmm.
Levels are powers of two and are either full or empty. So the total
item count tells you which levels are full or empty.
(gdb) print/t 1000000000
$3 = 111011100110101100101000000000
So no, definitely not reading 29 levels.
After realizing this, I have to be honest: I'm not finding your
hand-wavey dismissal of the technology convincing at all. :)
There's a *ton* of detail that they don't describe about how to actually
translate the logical notion of power-of-two node sizes into coherent
block IO that scales. I don't doubt that it's possible.
I very much doubt that the required complexity and cpu cost in the
kernel would be worth it for generic file system users, though. Hooo
boy, do I doubt it.
- z
next prev parent reply other threads:[~2012-03-28 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 14:25 Fractal Tree Indexing over B-Trees? Danny Piccirillo
2012-03-28 15:10 ` C Anthony Risinger
2012-03-28 18:42 ` Josef Bacik
2012-03-28 18:45 ` Jeff Mahoney
2012-03-28 18:57 ` Josef Bacik
2012-03-28 19:50 ` Zach Brown [this message]
2012-03-28 20:13 ` Josef Bacik
2012-03-28 20:29 ` Zach Brown
2012-03-28 20:44 ` Niels de Carpentier
2012-03-28 20:53 ` Josef Bacik
2012-03-28 21:14 ` Niels de Carpentier
2013-07-04 17:48 ` Kẏra
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=4F736B6F.2080805@zabbo.net \
--to=zab@zabbo.net \
--cc=danny.piccirillo@member.fsf.org \
--cc=josef@redhat.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;
as well as URLs for NNTP newsgroup(s).