[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209223#comment-15209223
]
ASF GitHub Bot commented on STORM-1632:
---------------------------------------
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-200553473
@arunmahadevan @HeartSaVioR Looking at the perf analysis from @roshannaik
It looks to be there is enough evidence to consider this as serious issue in
performance. Given that eventlogging is new feature and we do have evidence its
causing perf issue I am +1 on disabling it by default. I understand that once
they disabled they can't enable it in a running topology and that is OK. For
most usecases this might be used in dev cluster than a production cluster. Also
this is a blocker for 1.0 release , lets get this merged in and see if there is
a better a way to enable it by default and we can that in 1.1 release.
> 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)
