[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209475#comment-15209475
]
ASF GitHub Bot commented on STORM-1632:
---------------------------------------
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-200591500
We're debating six versus one half dozen. Do we disable it by default and
explicitly tell users they have to turn it on for the UI functionality to work?
Or do we enable it by default and tell users to disable it per topology to
realize a small performance gain?
I could go either way, but the latter seems like a better user experience
for users new to the feature.
Also, the minor performance hit is eclipsed by the performance improvements
in 1.0. And it can be easily turned off. It just needs to be documented
clearly, IMO.
> 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.
> **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)
