[
https://issues.apache.org/jira/browse/STORM-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279190#comment-15279190
]
Roshan Naik commented on STORM-1772:
------------------------------------
Hi [~mauzhang],
Yes thats it. I first observed that perf difference issue when working on
STORM-1632, but was not able to get to the bottom of it. The storm native
topology mentioned here :
https://github.com/apache/storm/pull/1217#issuecomment-201074919
I can try to locate the benchmark-specific version of the topology but its a
straightforward rewrite.
The storm native showed a difference of ~12% when doing a A/B test (with and
without the fix)
The benchmark specific version of the topology .. it was 25% as noted in the
description of STORM-1632.
IMO.. briefly ignoring the perf diff issue, it would be good to go ahead and
see what we can incorporate from that benchmark . In this jira my goal is to
add a few topologies for perf testing... not to create a benchmarking
tool/framework itself. In that sense its not conflicting with STORM-642.
*side note:* If we are adding a benchmarking framework, it would be good if it
can run standard Storm topologies directly and not require topologies to be
written specifically for it.
> Create topologies for measuring performance
> -------------------------------------------
>
> Key: STORM-1772
> URL: https://issues.apache.org/jira/browse/STORM-1772
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Roshan Naik
> Assignee: Roshan Naik
>
> Would be very useful to have some simple reference topologies included with
> Storm that can be used to measure performance both by devs during development
> (to start with) and perhaps also on a real storm cluster (subsequently).
> To start with, the goal is to put the focus on the performance
> characteristics of individual building blocks such as specifics bolts,
> spouts, grouping options, queues, etc. So, initially biased towards
> micro-benchmarking but subsequently we could add higher level ones too.
> Although there is a storm benchmarking tool (originally written by Intel?)
> that can be used, and i have personally used it, its better for this to be
> integrated into Storm proper and also maintained by devs as storm evolves.
> On a side note, in some instances I have noticed (to my surprise) that the
> perf numbers change when the topologies written for Intel benchmark when
> rewritten without the required wrappers so that they runs directly under
> Storm.
> Have a few topologies in mind for measuring each of these:
> # *Queuing and Spout Emit Performance:* A topology with a Generator Spout but
> no bolts.
> # *Queuing & Grouping performance*: Generator Spout -> A grouping method ->
> DevNull Bolt
> # *Hdfs Bolt:* Generator Spout -> Hdfs Bolt
> # *Hdfs Spout:* Hdfs Spout -> DevNull Botl
> # *Kafka Spout:* Kafka Spout -> DevNull Bolt
> # *Simple Data Movement*: Kafka Spout -> Hdfs Bolt
> Shall add these for Storm core first. Then we can have the same for Trident
> also.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
