[JCR-1196] Optimize queries for DescendantSelfAxisWeight/ChildAxisQuery

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Component/s: jackrabbit-core, query
• Assignee: Ard Schrijvers
• Reporter: Ard Schrijvers
• Created: 30/Oct/07 11:18
• Updated: 05/Mar/08 16:01
• Resolved: 30/Jan/08 13:45

Description

A query like

/documents/en/news//*[@modificationDate] 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

Issue Links

• relates to: JCR-1213 UUIDDocId cache does not work properly because of weakReferences in combination with new instance for combined indexreader