[
https://issues.apache.org/jira/browse/OAK-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106208#comment-15106208
]
Chetan Mehrotra commented on OAK-3878:
--------------------------------------
We can also solve this issue at DocumentStore level. Current the DocumentStore
caches result for all {{query}} calls. That logic can be changed to only cache
the result if both from and to key have same parent path as thats the case
which happens in normal JCR level traversal which we want to speed up. If the
key have different parent path then its most likely iteration over whole of
DocumentStore and caching would not help much
[[email protected]] [~mreutegg] Thoughts? Should we change the caching
strategy here?
> Avoid caching of NodeDocument while iterating in BlobReferenceIterator
> ----------------------------------------------------------------------
>
> Key: OAK-3878
> URL: https://issues.apache.org/jira/browse/OAK-3878
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Reporter: Chetan Mehrotra
> Priority: Minor
>
> {{BlobReferenceIterator}} in DocumentMK makes use if {{DocumentStore}} API to
> query the NodeDocument. This would cause all those NodeDocuments to be added
> to cache in DocumentStore. Due to this when blob gc is running cache usage
> would not be that effective due to all the associated churn.
> As these NodeDocument are only required for BlobGC logic and its not expected
> that this document would read again soon it would be better to skip caching
> of these documents within DocumentStore
> Similar requirement exist in VersionGC logic but there we use direct store
> based API which does not add such documents to the cache
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
