[
https://issues.apache.org/jira/browse/OAK-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006148#comment-16006148
]
Michael Dürig commented on OAK-5192:
------------------------------------
>From an offline discussion it seems the best ways forward here would be to
>understand the impact of active deletion (OAK-2808) and reducing the index
>update frequency to the segment store ([~chetanm], could you add an issue
>reference for this?).
In the longer term we should start sketching out a solution for indexing that
would not need to put so much volatile content into the repository at all. The
solution should probably cover some middle ground from what we had in
Jackrabbit 2 and we have now in Oak without suffering from the respective
problems (i.e. index corruption in JR2 and repository growth in Oak).
[~teofili], could you add an issue reference here?
> 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
> Assignee: Tommaso Teofili
> Labels: perfomance, scalability
> Fix For: 1.8, 1.7.3
>
> Attachments: added-bytes-zoom.png, diff.txt.zip
>
>
> 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)
