[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207785#comment-15207785
]
ASF GitHub Bot commented on STORM-1632:
---------------------------------------
Github user roshannaik commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-200143091
In my opinion, since this performance hit can be quite large, we should
definitely set eventLoggers=0 by default, and additionally the UI should also
disable the 'debug' button if eventLoggers=0
That will avoid the confusion to users that Arun was mentioning earlier...
This feature has some needless penalties and wasting CPU cycles even when not
in use.
I tried switching the clojure lookups into a java implementation .. but
that didnt help. So i don't see a way to speed up these lookups.
> 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... **30%**
> faster when event loggers = 0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
