jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martijn Hendriks (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2407) Make the disk space used by cached binary properties configurable
Date Thu, 26 Nov 2009 10:28:39 GMT

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

Martijn Hendriks commented on JCR-2407:

After having a look at the code I also think that this problem is specific for deployments
that use a BlobStore and not the DataStore. The DbDataStore seems to cache nothing on the
local file system (except when copyWhileReading is true but even then the temp file is deleted
after closing the stream). So repeated reads just stream the blob every time from the database?
If so, isn't this a performance issue?

I can see the performance advantages of caching the DB blob in the temp dir clearly.  Can
we add information about the disk usage to the Cache interface similar the getMemoryUsed method?
The PropertyState class should then also get a method similar to calculateMemoryFootprint
for the disk footprint. The CacheManager and Cache implementations can then use this additional
information to evict binary properties if necessary. This might fit in quite cleanly in the
current design :)

> 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.

View raw message