You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2017/09/23 09:22:03 UTC

[jira] [Commented] (OAK-6710) CommitMitigated merge policy should not reduce performance significantly

    [ https://issues.apache.org/jira/browse/OAK-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16177676#comment-16177676 ] 

Vikas Saurabh commented on OAK-6710:
------------------------------------

[~teofili], I've assigned this to you and scheduled for 1.8. Please change it if that doesn't seem right.

> 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)