[
https://issues.apache.org/jira/browse/OAK-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225210#comment-16225210
]
Tommaso Teofili commented on OAK-6710:
--------------------------------------
some benchmark results:
default MP
{noformat}
# SimpleSearchTest C min 10% 50% 90% max
N
Oak-Segment-Tar 1 59 63 68 74 161
876
# FullTextSearchTest C min 10% 50% 90% max
N
Oak-Segment-Tar-DS 1 986 1009 1403 2259 3053
40
# LucenePropertyFullTextTest C min 10% 50% 90% max
N
Oak-Segment-Tar-DS 1 221 221 221 221 221
1
{noformat}
mitigating
{noformat}
# SimpleSearchTest C min 10% 50% 90% max
N
Oak-Segment-Tar 1 58 62 67 72 88
896
# FullTextSearchTest C min 10% 50% 90% max
N
Oak-Segment-Tar-DS 1 828 848 943 1042 1125
64
# LucenePropertyFullTextTest C min 10% 50% 90% max
N
Oak-Segment-Tar-DS 1 225 225 225 225 225
1
{noformat}
> 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)
