jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Guggisberg <stefan.guggisb...@gmail.com>
Subject Re: Performance bottleneck
Date Wed, 18 Jan 2006 17:22:16 GMT
On 1/18/06, Brian Moseley <bcm@maz.org> wrote:
> On 1/18/06, Stefan Guggisberg <stefan.guggisberg@gmail.com> wrote:
> > there's no general rule of thumb but since jcr's model is inherently
> > hierarchical
> > personally i would try to make use of this feature when designing a
> > content model.
> well, yes, that is self evident. but high scale usage suggests that
> even individual levels of the hierarchy can become very large.
> you don't seem to be particularly interested in addressing the issue
> of performance degradation with large numbers of child nodes, so i
> guess this thread will serve as documentation that we have to address
> performance issues in our content models by introducing
> implementation-specific workarounds. or am i misrepresenting your
> level of interest?

probably ;) it's not really a matter of level of interest but rather
of priority.
i planned to have a look at the issue and try to verify myself laurent's claim
of bad performance but right now it's not on the top of my todo list...

> i for one certainly expect to support 10,000 users in cosmo. at the
> moment all users are stored as child nodes of the workspace root node.
> i suppose i will introduce some intermediary layers of nodes between
> the root and user nodes to cut down the number of children of any
> particular node. i'm not particularly happy with that solution,
> because it has a ripple effect on every part of my application, but if
> that's what jackrabbit forces me to do to scale, i will.

View raw message