jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <mreut...@day.com>
Subject Re: Fine tunning jcr query
Date Thu, 15 Oct 2009 20:33:12 GMT
Hi,

like queries with a prefix wildcard are usually expensive. for your
case you rather want to test the existence of the property:

/jcr:root/Catalogs/catalog_1/Servers//*[@serverID]

that's probably a lot faster.

regards
 marcel

On Mon, Oct 12, 2009 at 17:44, sidhama <sidhartha.mallik@wipro.com> wrote:
>
> Sir/Mam,
> I am executing the following query for getting the counts of Servers.
> -----------
> /jcr:root/Catalogs/catalog_1/Servers//*[jcr:like(@serverID, '%')]
> -----------
>
> It has around 150,000 nodes and it takes closely 26 secs for retrieving the
> results,
> I modified it to by removing <Servers> folder
> -----------
> /jcr:root/Catalogs/catalog_1//*[jcr:like(@serverID, '%')]
> -----------
>
> It is giving a response time of 19secs, can i reduce it further well below
> 6/7 secs?
>
> Please suggest if i could fine tune the query, why any jcr query executed
> first time takes a longer time, but subsquently takes less time?
>
> Thanks
> Sidharth
>
> --
> View this message in context: http://www.nabble.com/Fine-tunning-jcr-query-tp25858002p25858002.html
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
>
>

Mime
View raw message