[
https://issues.apache.org/jira/browse/STORM-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roshan Naik updated STORM-1632:
-------------------------------
Attachment: BasicTopology.java
uploading topology code to validate perf hit.
To use it: ..
1) Copy the java file into examples/storm-starter
2) Rebuild the storm-starter package using mvn.
3) Run topology as follows:
storm jar
/Users/rnaik/Projects/idea/storm/examples/storm-starter/target/storm-starter-1.0.0-SNAPSHOT.jar
-c topology.eventlogger.executors=0 -c topology.max.spout.pending=2000 -c
topology.disruptor.batch.size=10000 storm.starter.BasicTopology
and then again with {{topology.eventlogger.executors=1}}
I have set those additional 2 flags as they improved performance over the
defaults for this topology.
I normally let it run for about 11 min and then capture the 10 min window
metrics from UI page.
> 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
>
> Attachments: BasicTopology.java
>
>
> 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)
