Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of mslama@email.cz designates
 77.75.72.26 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=email.cz;
	h=To:Date:Reply-To:From:Received:Subject:Mime-Version:Message-Id:Content-Transfer-Encoding:Content-Type:X-Country:X-Abuse:X-Seznam-User:X-Virus-Info:X-Seznam-SPF:X-Seznam-DomainKeys;
	b=kwaVfGwkSmYRd8ZlYiaUTdZSMMvh3qA+oVwDUkaWJyEIp/c5RKBDkZ7fvnS6ARc0P
	8kLAa+8dnc4wtiKXo3x0fCNW9IoFUKUw1vtEJlyDF0tDM5OgcBvr1C2HsxuDRfzSbYI
	L2xOU0zB1bDMeyNFVcEc/5Tta5Zm1jEpm88wxE8=
To: users@jackrabbit.apache.org
Date: Fri, 03 Feb 2012 13:13:25 +0100 (CET)
Reply-To: mslama@email.cz
From: mslama@email.cz
Subject: =?us-ascii?Q?XPath=20query=20performance=20question?=
Mime-Version: 1.0
Message-Id: <98772.1177.1935-26405-1397053679-1328271205@email.cz>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;	charset="us-ascii"

Hi,

I have following use case:

I have about 2000 company nodes under node companies:
/companies/company[1]
/companies/company[2]
....
/companies/company[N]

I query for one company by property value - exact match, no wildcards. And result should contain just one node. For example I use query:

//companies/company[@calais='http://d.opencalais.com/er/company/ralg-tr1r/2c970a55-e08d-3af8-ad1d-3c46f341e749']

and then one call of NodeIterator.next to get unique (or first as there is no constraint on uniqueness) result. So there is no big resultset.

Property 'calais' is string type and when set it is unique ie. small number of company nodes may have this property either empty or missing. Property value can be up to 100chars long if it can make any difference for index.

When only one thread is running it takes 100-200ms. When 4 threads are running it is about 500ms on average. I used
profiler with sampling to get some profiling data. I seems to be too much provided that number on nodes is not that high
and it is using Lucene index. Calls of query.execute and nodeIterator.next take both about the same time.
When I checked thread dumps it uses Lucene index so it does not look like it scans all nodes.

Question: Is there any way how speedup this kind of lookup? The only way I found so far is to incorporate the most often property used for lookup to node path as session.getNode(path) is much faster.

I use Jackrabbit 2.2.9 and Postgres 9.1 for saving all data but Lucene index. It runs on JBoss 7.

I searched for Jackrabbit XPath performance but no match for my use case: 
a) exact property match without like/wildcards
b) small resultset - just one result item

Thanks

Marek