jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Serge Huber (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 Mon, 06 Dec 2010 07:30:12 GMT

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

Serge Huber commented on JCR-2830:
----------------------------------

Does anyone know how SQL-1 does it ? It seems from the code that it lazy loads the results,
but how can it do so if sorting is needed ?

Best regards,
  Serge Huber.

> 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
>    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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message