[ https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211274#comment-15211274 ]
ASF GitHub Bot commented on STORM-1632: --------------------------------------- Github user ptgoetz commented on the pull request: https://github.com/apache/storm/pull/1217#issuecomment-201105956 Yes, there is a performance hit. Especially in a single node cluster (don't know if you were running multiple workers), and networking doesn't come into play . I'm thinking of the big picture where you have multiple nodes. Then the numbers change, and it's not that big a hit. If we release with what we have now, I would leave things as is, and document that there's a performance benefit to turning it off. It's not hard to twiddle that flag. If we release as is, with this patch, the ui won't work as expected. Users will be confused, and anyone in a support role (I.e. Us) will be barraged with questions. And users will see a broken product. The performance hit here is also minor compared to the performance gain from simply upgrading to Krio 3. I think this is an important issue to address, but I don't think it's that big a deal that it should block the 1.0 release. We can address it better later in a minor release. Let's get 1.0 out the door. -1 > 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 > > Attachments: BasicTopology.java > > > 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. > **Update:** with acker=0 the observed impact was much higher... **25%** > faster when event loggers = 0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)