jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Strasser (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-20) Logging into a repository with a big version history takes a long time
Date Fri, 19 Nov 2004 09:26:36 GMT
     [ http://nagoya.apache.org/jira/browse/JCR-20?page=comments#action_55664 ]
Tobias Strasser commented on JCR-20:

currently, the virtual item state provider of the version store acts like a persistent state
provider and does not create items for every session. 

it is true, that all versions are loaded (twice) in memory. once in the internal representation,
and once in the virtual state. both can be done more dynamically.

> Logging into a repository with a big version history takes a long time
> ----------------------------------------------------------------------
>          Key: JCR-20
>          URL: http://nagoya.apache.org/jira/browse/JCR-20
>      Project: Jackrabbit
>         Type: Bug
>  Environment: Jackrabbit SVN 76106
>     Reporter: Felix Meschberger
>     Assignee: Tobias Strasser
>     Priority: Critical

> Wenn a SessionImpl instance is created, the VersionManager.getVirtualItemStateProvider
method is called. This method - amongst other things - loads the complete (!) version history
into memory and walks through it to do some mapping.
> Besides taking a long time (near 1 minute just to get the version history through PersistentVersionManager.getVersionHistories())
mapping the version histories ultimately results in an "OutOfMemoryError".
> Currently there are 768 version histories and this is only a very small fraction of the
expected final number of version histories in my application

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message