[
https://issues.apache.org/jira/browse/METRON-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426199#comment-16426199
]
ASF GitHub Bot commented on METRON-1367:
----------------------------------------
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/873
Well, if it helped, cool, let’s keep it... was just curious about your use
case and whether we should have a bolder scope or if there is anything like
this that would help elsewhere in general performance debugging. I’m certainly
not against this in any way. :)
> On 4 Apr 2018, at 22:21, ottobackwards <[email protected]> wrote:
>
> I'm shelving this. Thinks for taking a look.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
>
> Stellar should optionally instrument function calls
> ---------------------------------------------------
>
> Key: METRON-1367
> URL: https://issues.apache.org/jira/browse/METRON-1367
> Project: Metron
> Issue Type: Improvement
> Reporter: Otto Fowler
> Assignee: Otto Fowler
> Priority: Major
>
> It would be nice if stellar processor(s) could optionally instrument function
> calls to test performance.
> The result would be some structure with the calls, the times and maybe some
> context as a list or map
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
