[ https://issues.apache.org/jira/browse/OAK-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189320#comment-16189320 ]
Thomas Mueller commented on OAK-6710: ------------------------------------- [~teofili] not sure if you are aware of this, but it looks like performance degradation was not because of the CommitMitigated merge policy, but because of OAK-6717 (as far as I understand, [~chetanm] please correct me if I'm wrong). So possibly this issue here can be resolved "won't fix"? > CommitMitigated merge policy should not reduce performance significantly > ------------------------------------------------------------------------ > > Key: OAK-6710 > URL: https://issues.apache.org/jira/browse/OAK-6710 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: lucene > Affects Versions: 1.7.7 > Reporter: Vikas Saurabh > Assignee: Tommaso Teofili > Labels: performance, scalability > Fix For: 1.8 > > > While running performance tests (internally) using latest unstable releases > having {{CommitMitigatedTieredMergePolicy}} we observed significant drop in > performance (OAK-6704). > The policy, although bad for performance, showed dramatic drop in churn > created in data store size. So, clearly, OAK-5192 did what it intended to do. > Opening this issue to factor in drop in performance and then set the default > back to {{CommitMitigatedTieredMergePolicy}}. -- This message was sent by Atlassian JIRA (v6.4.14#64029)