[jira] [Comment Edited] (JCR-3477) Lazy query result sets

["Michael Dürig (JIRA)" <ji...@apache.org>]

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

Michael Dürig edited comment on JCR-3477 at 12/5/12 9:21 AM:
-------------------------------------------------------------

I have so far seen it for queries of type

   /jcr:root/root//element(*) 

when the tree rooted at "root" is large (no flat hierarchies involved). I.e. ~110k nodes bumps memory usage up to 400MB on Query.execute(). 
                
      was (Author: mduerig):
    I have so far seen it for queries of type

   /jcr:root/root//element(*) 

when the tree rooted at "root" is large. I.e. ~110k nodes bumps memory usage up to 400MB on Query.execute(). 
                  
> Lazy query result sets 
> -----------------------
>
>                 Key: JCR-3477
>                 URL: https://issues.apache.org/jira/browse/JCR-3477
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Alex Parvulescu
>            Priority: Minor
>
> Following JCR-3472, I'd like to open a discussion on what can be reasonably expected from a query that does/can do lazy fetching of results.
> Creating ~110k nodes and fetching them all looks like it goes in the vicinity of 400mb of memory, so the default 256mb setup for tests is not sufficient to run such a test, as we've already seen on JCR-3472.
> What are the expectations around lazy loading and queries that can potentially hit a high number of nodes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira