jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-3477) Lazy query result sets
Date Wed, 05 Dec 2012 07:46:59 GMT

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

Marcel Reutegger commented on JCR-3477:

At least my expectation is that Jackrabbit should be able to handle large result sets with
reasonable memory usage. Do we have more details on what exactly consumes that much memory?
Is it specific to some queries or is it for any kind of query?
> 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

View raw message