You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2017/05/03 06:37:05 UTC
[jira] [Commented] (OAK-5192) Reduce Lucene related growth of
repository size
[ https://issues.apache.org/jira/browse/OAK-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15994348#comment-15994348 ]
Thomas Mueller commented on OAK-5192:
-------------------------------------
An alternative to changing the merge policy might be to use NRT indexes, so that the index in the repository is updated much less frequently, for example every 5 minutes. See also the [comment OAK-2808|https://issues.apache.org/jira/browse/OAK-2808?focusedCommentId=15994345&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15994345].
Another alternative is to use asynchronous property indexes. It would be interesting to know the relative size / growth comparing asynchronous property indexes vs. asynchronous Lucene property indexes.
> Reduce Lucene related growth of repository size
> -----------------------------------------------
>
> Key: OAK-5192
> URL: https://issues.apache.org/jira/browse/OAK-5192
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene, segment-tar
> Reporter: Michael Dürig
> Labels: perfomance, scalability
> Fix For: 1.8
>
> Attachments: added-bytes-zoom.png
>
>
> I observed Lucene indexing contributing to up to 99% of repository growth. While the size of the index itself is well inside reasonable bounds, the overall turnover of data being written and removed again can be as much as 99%.
> In the case of the TarMK this negatively impacts overall system performance due to fast growing number of tar files / segments, bad locality of reference, cache misses/thrashing when looking up segments and vastly prolonged garbage collection cycles.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)