[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214769#comment-15214769
]
ASF GitHub Bot commented on STORM-1632:
---------------------------------------
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-202556630
It should be fairly easy to alter the UI to make it clear to users when
this is disabled, as well as how to enable it. If we can do that I would
support disabling it by default (i.e. I would be +1).
My main objection with this patch is that will make the UI appear broken by
default and confuse users, especially new users.
> 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)
