[
https://issues.apache.org/jira/browse/OAK-5192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072562#comment-16072562
]
Tommaso Teofili edited comment on OAK-5192 at 7/3/17 2:55 PM:
--------------------------------------------------------------
I've added a multiplier parameter so that the _add, reindex, add/delete_
workflow can be executed multiple times and see how the index grows over time
using different configurations.
See the attached graph
https://issues.apache.org/jira/secure/attachment/12875524/Screen%20Shot%202017-07-03%20at%2016.50.00.png.
After ten runs these are the respective sizes:
||Codec||Size||
|oakCodec|5700 MB|
|Lucene46|5300 MB|
|customCodec|5000 MB|
was (Author: teofili):
I've added a multiplier parameter so that the _add, reindex, add/delete_
workflow can be executed multiple times and see how the index grows over time
using different configurations.
See the attached graph
https://issues.apache.org/jira/secure/attachment/12875524/Screen%20Shot%202017-07-03%20at%2016.50.00.png.
After ten runs these are the respective sizes:
||Codec||Size||
|oakCodec|5700|
|Lucene46|5300|
|customCodec|5000|
> 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)
