jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-2295) Using "order by jcr:score" slows down queries by a few orders of magnitude
Date Wed, 25 Feb 2015 14:17:05 GMT

     [ https://issues.apache.org/jira/browse/OAK-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Mueller resolved OAK-2295.
---------------------------------
    Resolution: Won't Fix

The case "order by @jcr:score descending" (hits with the biggest score first) is now fast.

The case "order by @jcr:score" (ascending) is still slow, and I don't think that needs to
be fixed, so I set this issue to "won't fix".



> Using "order by jcr:score" slows down queries by a few orders of magnitude
> --------------------------------------------------------------------------
>
>                 Key: OAK-2295
>                 URL: https://issues.apache.org/jira/browse/OAK-2295
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: oak-lucene
>    Affects Versions: 1.0.8
>         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
>            Reporter: Punyanjan Sen
>            Assignee: Thomas Mueller
>            Priority: Critical
>             Fix For: 1.1.7, 1.0.13
>
>         Attachments: OAK-2295.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message