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

ASF GitHub Bot commented on METRON-1367:
----------------------------------------

Github user simonellistonball commented on the issue:

    https://github.com/apache/metron/pull/873
  
    Did it work out for you to find bottlenecks @ottobackwards ? I would be 
more inclined to do multi-run micro-benchmarking (I have a bunch of 
multi-sample perfidix runs on all the parser work I've done for example) rather 
than a one of timer. Would a more 'proper' run it a thousand times in the 
proper context of the topology code performance profiler be useful / relevant. 
Did you get the info you need from this as a quicker (and quite possibly good 
enough!) approach?


> 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)

Reply via email to