[
https://issues.apache.org/jira/browse/TINKERPOP-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15088476#comment-15088476
]
Bob Briody commented on TINKERPOP-958:
--------------------------------------
"Additionally, if the TraversalMetrics are cap'd off the end of the traversal
then this step and the duration it takes should be excluded from the metrics
and timers."
[~okram], how do you feel about me splitting off this portion of work into a
separate ticket, bangin it out right quick, and PR'ing it to master?
> Improve usability of .profile() step.
> -------------------------------------
>
> Key: TINKERPOP-958
> URL: https://issues.apache.org/jira/browse/TINKERPOP-958
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Reporter: Bob Briody
> Assignee: Marko A. Rodriguez
> Fix For: 3.2.0-incubating
>
>
> The .profile() step is currently tedious to use. One must remember this
> entire string to activate profiling and cap off the result:
> "profile().cap(TraversalMetrics.METRICS_KEY)".
> This should be streamlined.
> Additionally, if the TraversalMetrics are cap'd off the end of the traversal
> then this step and the duration it takes should be excluded from the metrics
> and timers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
