You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/09/29 04:43:05 UTC
[jira] [Updated] (STORM-642) Add Storm Benchmarking Framework
[ https://issues.apache.org/jira/browse/STORM-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Kellogg updated STORM-642:
-------------------------------
Component/s: (was: external)
> Add Storm Benchmarking Framework
> --------------------------------
>
> Key: STORM-642
> URL: https://issues.apache.org/jira/browse/STORM-642
> Project: Apache Storm
> Issue Type: Improvement
> Reporter: P. Taylor Goetz
> Assignee: P. Taylor Goetz
>
> (This is intended to be a parent for a multi-task JIRA)
> Add a framework for benchmarking Storm topologies and clusters that would capture basic throughput (messages/sec., MB/sec.) and latency metrics.
> Allow for the definition of named "benchmark suites" in a configuration file (i.e. YAML) that would define multiple runs of the same benchmark with different tuning parameters (# workers, parallelism hints, etc.). This would allow for easy comparison of different runs to show how different tuning options affect overall performance.
> Develop and benchmark both Core Storm and Trident Topologies to illustrate the difference in performance characteristics. Benchmark multiple trident constructs (joins, aggregations, partition(Persist), etc.) to illustrate performance implications.
> Document results in a blog post series "Benchmarking Storm" on storm.apache.org/blog.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)