[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221061#comment-15221061
]
ASF GitHub Bot commented on STORM-1632:
---------------------------------------
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-204224677
Thanks for the last-minute effort @roshannaik.
+1
I typically like to wait for 24 hrs. after the last commit on a PR to
merge, even though it's not required by our bylaws.
I intend to merge this earlier in the interest of getting the 1.0 release
out. If there are any objections after the fact, there will plenty of time to
cancel the VOTE, revert, etc.
> 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
> 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)
