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

ASF GitHub Bot commented on STORM-1632:
---------------------------------------

Github user arunmahadevan commented on the pull request:

    https://github.com/apache/storm/pull/1217#issuecomment-199235692
  
    @roshannaik profiled "org.apache.storm.starter.ExclamationTopology" after 
setting log level to ERROR and the `send_to_eventlogger` doesn't show up in the 
top 25 methods in terms of CPU time. Tried with different configurations (one 
worker, three workers, increased and reduced the spout and bolt parallelism) 
but the results were more or less the same. 
    
    
![profile-3-3](https://cloud.githubusercontent.com/assets/6792890/13916942/c480e89a-ef83-11e5-97f3-e4c0978dd8c5.png)



> Disable event logging by default
> --------------------------------
>
>                 Key: STORM-1632
>                 URL: https://issues.apache.org/jira/browse/STORM-1632
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>            Reporter: Roshan Naik
>            Assignee: Roshan Naik
>            Priority: Blocker
>             Fix For: 1.0.0
>
>
> EventLogging has performance penalty. For a simple speed of light topology  
> with a single instances of a spout and a bolt, disabling event logging 
> delivers a 7% to 9% perf improvement (with acker count =1)
> Event logging can be enabled when there is need to do debug, but turned off 
> by default.



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

Reply via email to