[ https://issues.apache.org/jira/browse/OAK-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044339#comment-16044339 ]
Tommaso Teofili edited comment on OAK-5192 at 6/9/17 11:49 AM: --------------------------------------------------------------- attaching a unit test for testing how different Lucene configurations impact on segment store size. The first (strange) thing that turns out is that the file store size is bigger with _OakCodec_ than with _Lucene46_ codec: 149MB (Lucene46) vs 160MB (OakCodec). was (Author: teofili): attaching a unit test for testing how different Lucene configurations impact on segment store size. > 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, OAK-5192.0.patch > > > 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)