[OAK-2295] Using "order by jcr:score" slows down queries by a few orders of magnitude

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Won't Fix
• Affects Version/s: 1.0.8
• Fix Version/s: 1.0.13, 1.1.7
• Component/s: lucene

Environment

Linux 2.6.32-431.23.3.el6.x86_64 VM,
16GB RAM
4 Core Intel(R) Xeon(R) CPU E5-4640 0 @ 2.40GHz

• Assignee: Thomas Mueller
• Reporter: Punyanjan Sen
• Created: 25/Nov/14 19:52
• Updated: 08/Oct/19 15:21
• Resolved: 25/Feb/15 14:16

Description

The following query takes over 16 seconds to run on our QA system:
/jcr:root/content/help/en//*[jcr:contains(., 'illustrator')] order by jcr:score

Removing the "order by jcr:score" reduces the query time to 14ms

The time taken increases linearly with the amount of content in our repository.

Sub-Tasks

• Support for "order by jcr:score descending" in lucene property index: Closed