[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209253#comment-15209253
]
ASF GitHub Bot commented on STORM-1632:
---------------------------------------
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/1217#issuecomment-200559629
I did a quick benchmark on a real cluster (albeit on a VMware cluster) and
found that there was a throughput hit, but it was small -- about 0.4%.
I'm okay with leaving the defaults as is, and documenting how to disable
the feature.
If there's a better solution, I'm okay with waiting for a post 1.0 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)
