[
https://issues.apache.org/jira/browse/JCR-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782400#action_12782400
]
Stefan Guggisberg commented on JCR-2407:
----------------------------------------
> The fact that we now use only a single database connection is the core reason
> for why we need to pull the full binary already during the
> PersistenceManager.load() call instead of streaming it to the client directly
> from the database.
no, the main reason was to allow repeated reads without requiring
server-roudtrips... performance of blob handling in db's is usually very
slooooooow (at l;east in my experience).
> Make the disk space used by cached binary properties configurable
> -----------------------------------------------------------------
>
> Key: JCR-2407
> URL: https://issues.apache.org/jira/browse/JCR-2407
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Affects Versions: 2.0-beta1
> Reporter: Martijn Hendriks
> Attachments: repository.xml, workspace.xml
>
>
> Binary properties which are in Jackrabbit's caches (SharedItemStateManager
> eg) are stored on disk in the temp dir. This can cause problems on small
> temporary file systems as the size of the binary properties on disk is not
> limited by Jackrabbit. There is one way to influence this indirectly: make
> the Jackrabbit cache sizes smaller (via the CacheManager). It could be
> helpful in some cases if an upper bound on the disk usage can be given.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
