Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 49030 invoked from network); 22 Jun 2007 09:47:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jun 2007 09:47:28 -0000 Received: (qmail 4865 invoked by uid 500); 22 Jun 2007 09:47:30 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 4840 invoked by uid 500); 22 Jun 2007 09:47:30 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 4830 invoked by uid 99); 22 Jun 2007 09:47:30 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jun 2007 02:47:30 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of marcel.reutegger@gmx.net designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 22 Jun 2007 02:47:26 -0700 Received: (qmail invoked by alias); 22 Jun 2007 09:47:04 -0000 Received: from l2tp.day.com (EHLO [192.168.10.5]) [62.192.10.243] by mail.gmx.net (mp054) with SMTP; 22 Jun 2007 11:47:04 +0200 X-Authenticated: #894343 X-Provags-ID: V01U2FsdGVkX18o9r5UVxUovlef/+JHD81sNScdW4jx3HSmsr6R05 voXUYDzS2okD2t Message-ID: <467B9A98.1040807@gmx.net> Date: Fri, 22 Jun 2007 11:47:04 +0200 From: Marcel Reutegger User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: dev@jackrabbit.apache.org Subject: Re: About Jackrabbit repository model References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org Fr�d�ric Esnault wrote: > Your performance tests were not made with same name siblings I guess? Because > mine, with 12K same name siblings child nodes, a simple search is awful. Not > a search on something like //lgw:contract[5], which is fast, but even > /jcr:root/lgw:root/lgw:contracts/lgw:contract is an awful query.... the default configuration in jackrabbit uses document order on the nodes in a query result. for larger result sets this is know to be slow because it reads the nodes from the persistence manager. sibling ordering information is not present in the index. did you try to disable document order? you can add the following parameter to the SearchIndex tag in the workspace.xml file: regards marcel