[
https://issues.apache.org/jira/browse/OAK-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-5192:
-------------------------------
Attachment: diff.txt.zip
Attached a diff ([^diff.txt.zip]) across 1000 subsequent commits of the sites
longevity test limited to content at {{root/oak:index/lucene}}. Each diff
consists of the time stamp of the respective revision followed by a list of
changes. There are fewer than 999 diffs as I left out the empty ones.
These changes account for 7415993 bytes added in total and 7427450 bytes
removed in total to/from the segment store (that is binaries that went to the
blob store are excluded from these numbers).
[~chetanm], is this what you needed?
> 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)
