jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-8029) Additional merge metrics
Date Thu, 07 Feb 2019 13:30:00 GMT

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

Marcel Reutegger commented on OAK-8029:
---------------------------------------

Added two new metrics:
- {{DOCUMENT_NS_MERGE_CHANGES_RATE}}: this meter tracks the number of merged changes.
- {{DOCUMENT_NS_MERGE_SUCCESS_NORMALIZED_TIME}}: this timer records the normalized time it
took to perform a merge. Normalization is done by dividing the absolute merge time by the
number of merged changes.

Implemented in trunk: http://svn.apache.org/r1853131

> Additional merge metrics
> ------------------------
>
>                 Key: OAK-8029
>                 URL: https://issues.apache.org/jira/browse/OAK-8029
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.12
>
>
> The current merge metrics lack insight how big a merge was. This improvement is about
adding a metric that tracks the number of changes written by a merge. In addition there should
be a metric that puts the merge time into relation of the number of changes. Only the absolute
time of a merge, as available right now, is not a good indicator whether performance of those
operations are OK.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message