Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Sat, 13 Aug 2011 12:05:27 +0000 (UTC)
From: "Alex Parvulescu (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: 
 <730015048.35858.1313237127188.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <28227677.91591291373592428.JavaMail.jira@thor>
Subject: [jira] [Commented] (JCR-2830) JCR-SQL2 : Query on large node-set is
 (too) slow even when offset and limit is used
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alex Parvulescu commented on JCR-2830:
--------------------------------------

yes, the patch is old, and will soon be rendered obsolete by JCR-2959

> 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