[ https://issues.apache.org/jira/browse/OAK-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16077882#comment-16077882 ]
Tommaso Teofili commented on OAK-5192: -------------------------------------- I've run again my tests, here're the results: ||codec||mergePolicy||repoSize||FDS size||time|| |oakCodec|default|578.4 MB|4 GB|8 min| |Lucene46|default|578.0 MB|4 GB|12 min| |customCodec|default|577.9 MB|4 GB|14 min| |oakCodec|no|833.1 MB|5 GB|3 min| |Lucene46|no|577.7 MB|3 GB|6 min| |customCodec|no|577.8 MB|3 GB|12 min| > 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.8 > > Attachments: added-bytes-zoom.png, binSize100.txt, binSize16384.txt, > binSizeTotal.txt, diff.txt.zip, nonBinSizeTotal.txt, OAK-5192.0.patch, Screen > Shot 2017-07-03 at 16.50.00.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.4.14#64029)