[ 
https://issues.apache.org/jira/browse/JCR-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560945#action_12560945
 ] 

Ard Schrijvers commented on JCR-1196:
-------------------------------------

The above numbers are done with Jackrabbit trunk or 1.4 or an older version?  
In JCR-1213 we fixed the caching issue regarding 
DescendantSelfAxisWeight/ChildAxisQuery . Obviously, the caching is only 
measurable in consecutive calls. So perhaps Martin Zdila could do a new test 
with Jackrabbit 1.4, and specifically look at the time used for consecutive 
calls. That the first call takes longer we are aware of (though one single 
slower query at startup is perhaps acceptable).

Shouldn't we close this issue since JCR-1213 is fixed and create a new one 
'first execution for queries for DescendantSelfAxisWeight/ChildAxisQuery are 
slow when the number of hits is large and the parent nodes are divided over 
many different lucene indexes'. We largely resolved this issue by fixing the 
cache IMO. WDOT? 

> Optimize queries for DescendantSelfAxisWeight/ChildAxisQuery
> ------------------------------------------------------------
>
>                 Key: JCR-1196
>                 URL: https://issues.apache.org/jira/browse/JCR-1196
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core, query
>            Reporter: Ard Schrijvers
>
> A query like 
> /documents/en/news//[EMAIL PROTECTED] order by @modificationDate
> when  there are many nodes ( > 1.000) in  /documents/en/news becomes very 
> slow. I think the bottleneck is in something like recursive filters in 
> lucene. First off all I'll try to find some stastistics about the 
> performance, and describe the bottleneck. After that, a solution must be 
> found, where we need to keep in mind that 
> 1) these queries run faster and scale better (obviously)
> 2) moving a node must stay a cheap operation
> Also see:
> http://www.nabble.com/Search-performance--%3A-MultiIndex-tf4695559.html#a13421949

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to