[
https://issues.apache.org/jira/browse/STORM-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005956#comment-14005956
]
ASF GitHub Bot commented on STORM-297:
--------------------------------------
Github user miguno commented on the pull request:
https://github.com/apache/incubator-storm/pull/103#issuecomment-43896389
@clockfly Many thanks for your all the hard work and your patience. It's
much appreciated!
I don't have anything to add to the discussion at the moment (thanks Bobby
& Co.!) except that I, too, can confirm that the Storm test suite passes with
Sean's latest code changes. I tested against the latest commit in Sean's
`storm_async_netty_and_batch_api` branch, which at the time of writing was
https://github.com/clockfly/incubator-storm/commit/20b4f8b2195a1bf214f63e10b1bbca4690c0290f.
$ git checkout master
$ gco -b STORM-297
$ git pull [email protected]:clockfly/incubator-storm.git
storm_async_netty_and_batch_api
$ mvn clean install
>>> Success.
PS: Unfortunately I haven't had the chance yet to run the patched version
of Storm in a large-scale environment.
> Storm Performance cannot be scaled up by adding more CPU cores
> --------------------------------------------------------------
>
> Key: STORM-297
> URL: https://issues.apache.org/jira/browse/STORM-297
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Reporter: Sean Zhong
> Labels: Performance, netty
> Fix For: 0.9.2-incubating
>
> Attachments: Storm_performance_fix.pdf,
> storm_Netty_receiver_diagram.png, storm_performance_fix.patch
>
>
> We cannot scale up the performance by adding more CPU cores and increasing
> parallelism.
> For a 2 layer topology Spout ---shuffle grouping--> bolt, when message size
> is small (around 100 bytes), we can find in the below picture that neither
> the CPU nor the network is saturated. When message size is 100 bytes, only
> 40% of CPU is used, only 18% of network is used, although we have a high
> parallelism (overall we have 144 executors)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
