[
https://issues.apache.org/jira/browse/OAK-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006445#comment-16006445
]
Michael Dürig commented on OAK-5192:
------------------------------------
Attached [^binSize100.txt], [^binSize16384.txt], [^binSizeTotal.txt] and
[^nonBinSizeTotal.txt] with the sizes for binaries <= 100, <=16384 and <=
Long.MaxValue and the sizes for non binaries per revision in [^diff.txt.zip],
respectively.
Total sum of sizes are: 44785 bytes, 5887029, bytes, 237895837 bytes and 245128
bytes listed in the same order as above.
Script used for this analysis:
https://gist.github.com/mduerig/f79981bbf15c6e21f0085a10a43106fb
> 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, binSize100.txt, binSize16384.txt,
> binSizeTotal.txt, diff.txt.zip, nonBinSizeTotal.txt
>
>
> 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)
