[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211333#comment-15211333
]
ASF GitHub Bot commented on STORM-1632:
---------------------------------------
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-201116132
@ptgoetz I understand it is not hard to change the config. But the default
behavior shouldn't be affecting peformance. Going to 1.0 can hit 9% perf hit
just because we are shipping a new feature that can cause performance issue .
UI can be fixed in the same patch as well. Just don't show the buttons on the
UI if the event.loggers are set to 0. Its a SIMPLE FIX
> 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)
