jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-2830) JCR-SQL2 : Query on large node-set is (too) slow even when offset and limit is used
Date Sat, 13 Aug 2011 08:18:27 GMT

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

Jukka Zitting commented on JCR-2830:
------------------------------------

Note that we need to take also ACL processing into account when evaluating the offset and
limit settings. Also, the offset and limit settings only make sense when combined with an
ORDER BY statement, which is why we need to implement JCR-2959 first before the proposed approach
has a chance of working correctly.

> JCR-SQL2 : Query on large node-set is (too) slow even when offset and limit is used
> -----------------------------------------------------------------------------------
>
>                 Key: JCR-2830
>                 URL: https://issues.apache.org/jira/browse/JCR-2830
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: query
>    Affects Versions: 2.3.0
>         Environment: + Win7 (64bit)
> + JR built from latest greatest sources
> + repo with many nodes of same node type > 77'000
>            Reporter: Clemens Wyss
>         Attachments: JCR-2830.patch
>
>
> Given a node-set of approx 77'000 entries a SQL2-query limited to 10 nodes takes approx
37 to 59sec (!) whereas the corresponding SQL returns in less than  1sec.
> Query q = session.getWorkspace().getQueryManager().createQuery( "select * from [task]",
Query.SQL2 );
> q.setOffset( 0 ); // or any other offset
> q.setLimit( 10 ); 
> returnValue = q.execute();

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message