From: Hans Reiser <reiser@namesys.com>
To: venom@sns.it
Cc: Steve Glines <sglines@is-cs.com>, linux-kernel@vger.kernel.org
Subject: Re: file system technical comparisons
Date: Wed, 07 Jan 2004 12:13:06 +0300 [thread overview]
Message-ID: <3FFBCDA2.9040503@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0401070036190.19759-100000@cibs9.sns.it>
venom@sns.it wrote:
>On Tue, 6 Jan 2004, Hans Reiser wrote:
>
>
>
>>balanced trees squish things together at every modification of the
>>tree. Dancing trees squish things together when they get low on ram,
>>which is less often. this means that we can afford to squish tighter
>>because we do it less often.
>>
>>
>
>This is generally true except some maior cases.
>
>A SAP server, for example, is "always" low on ram, not because of oracle, but
>because how the "disp+work" processes work.
>
>Another case I am thinking is a tibco server, when processes start to fork
>because of a lot of incoming messages from everywhere, and the DB really start
>to write a lot of stuff (all small writes).
>
>I am curious to make some test in those cases.
>
>
even if it is always low on ram, the memory pressure signal from VM is
still less often than the tree modification because we squish in big
batches.
>Another think I am thinking about is an MC^2 lun. If all the I/O is resolved
>inside of the EMC cache, BTrees could be better than dancing trees?
>
no, dancing trees would still fit in that cache and still be more cpu
efficient
> In fact
>in this case what matters is the CPU power you are using, since you de facto
>talk just with EMC cache.
>
>I know those are strange scenarios, but those are the scenarios I am actually
>working with. Since those are not typical situations, I think right now they are
>ininfluent, but in the future maybe more people will have to deal with them.
>
>Anyway untill I do not make some serious experiment mine are just
>speculations.
>
>Luigi
>
>
>
>
>
there are flaws in the reiser4 algorithms, but the dancing tree concept
is a good one. We are currently experimentally encountering various
oddities needing fixing. For instance, if your working set is just
barely too large for ram, we have a tendency to flush too many pages out
of ram and make you wait for us to do so. this is fixable, and being
discussed now amongst us.
--
Hans
next prev parent reply other threads:[~2004-01-07 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 21:38 file system technical comparisons Steve Glines
2004-01-05 9:42 ` venom
2004-01-05 11:04 ` Hans Reiser
2004-01-05 17:08 ` venom
2004-01-05 17:18 ` Hans Reiser
2004-01-06 11:58 ` venom
2004-01-06 12:07 ` Hans Reiser
2004-01-06 23:48 ` venom
2004-01-07 9:13 ` Hans Reiser [this message]
2004-01-05 17:37 ` Randy.Dunlap
2004-01-06 12:04 ` venom
2004-01-06 14:55 ` Hans Reiser
2004-01-06 20:32 ` Theodore Ts'o
2004-01-09 19:32 ` Stewart Smith
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=3FFBCDA2.9040503@namesys.com \
--to=reiser@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sglines@is-cs.com \
--cc=venom@sns.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.