You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "Bob Briody (JIRA)" <ji...@apache.org> on 2015/09/14 17:04:45 UTC

[jira] [Commented] (TINKERPOP3-697) Allow setting time on MutableMetrics

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

Bob Briody commented on TINKERPOP3-697:
---------------------------------------

[~okram] this ticket should be closed.

> Allow setting time on MutableMetrics
> ------------------------------------
>
>                 Key: TINKERPOP3-697
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-697
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.0.1-incubating
>            Reporter: Matthias Broecheler
>            Assignee: Bob Briody
>
> Currently, MutableMetrics must be explicitly started and stopped to measure time. However, TP3 might be implemented by a graph db which has an internal metrics and profiling framework from which the TP3 metrics are being populated. In this case, it should be possible to simply set the time on a mutable metric.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)