[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roshan Naik updated STORM-1632:
-------------------------------
Description:
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
with event loggers = 0
was:
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.
> 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 with event loggers = 0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
