[
https://issues.apache.org/jira/browse/TINKERPOP3-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532785#comment-14532785
]
Bob Briody commented on TINKERPOP3-665:
---------------------------------------
This ticket would result in an enhancement to the MutableMetrics class. Right
now there is a method to add independent nested metrics. Another method would
be added to enable the addition of aggregate nested metrics. For example, there
are cases where Titan makes many sequential calls to the DB backend. It is
beneficial to capture the individual duration of each of these calls, but in
most cases a user will just want to see the total duration. The Metrics
implementation would aggregate each of these Metrics instances while also
providing a way to inspect them individually.
> Consider supporting aggregated nested metrics in Metrics Framework
> ------------------------------------------------------------------
>
> Key: TINKERPOP3-665
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-665
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Reporter: Bob Briody
> Priority: Minor
>
> The Metrics Framework supports nested metrics, which is good for most
> underlying operations. However, there are cases where many similar operations
> can be grouped together, such as a vendor implementation that makes many
> similar calls to a DB or Index. The Metrics Framework should provide the
> ability to aggregate these operations into a single entity without losing
> information about each individual operation such as it's duration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
