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

["Thomas Mueller (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14336516#comment-14336516 ] 

Thomas Mueller commented on OAK-2295:
-------------------------------------

As OAK-2353 is already applied, I think we no longer need changes in the query engine. With the current code, "order by @jcr:score descending" are handled by the (new) Lucene index, and the query engine doesn't sort.

If you use "order by @jcr:score" (without the "descending"), then the query engine will still sort. But I think that's OK, because I don't see a use case why someone would sort by jcr:score in ascending order (the nodes with the lowest score first).

[~psen], is this OK for you?

> 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)