jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <bdelacre...@apache.org>
Subject Re: Jackrabbit & Performance
Date Wed, 20 Nov 2013 19:38:51 GMT

On Wed, Nov 20, 2013 at 11:39 AM, Enrique Medina Montenegro
<e.medina.m@gmail.com> wrote:
> ...For example, instead of doing à session.getNode(“/marks/000345123”) ß we
> could query à SELECT * FROM [iptool:markType] WHERE [iptool:id] =
> ‘000345123’...

This is typically where you don't want to use queries in JCR.

If you split your mark ID in multiple levels as suggested in this
thread, you'll end up with paths like /mark/123/456/789 and
session.getNode("/mark/123/456/789") should be much faster than
queries, or something's very wrong.

It looks like your performance problems come from putting too many
nodes under the same parent - Jackrabbit is not designed for that so
you're going against the current.


View raw message