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

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

Github user arunmahadevan commented on the pull request:

    https://github.com/apache/storm/pull/1217#issuecomment-199754698
  
    @roshannaik I ran the Exclamation topology with the TestWordSpout emitting 
a tuple every 10 ms with a spout parallelism of 10 and measured the throughput 
with and without event logger and I observed almost the same results. 
    
    I am also attaching the Jprofiler output after tracing the topology for 
about 1.36 Million tuples where the send_to_eventlogger is consuming only 
around 0.2% time.
    
    <img width="1220" alt="spout" 
src="https://cloud.githubusercontent.com/assets/6792890/13949426/fac1a5ee-f04a-11e5-95f1-f5d9a412ff77.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