[
https://issues.apache.org/jira/browse/STORM-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013488#comment-14013488
]
ASF GitHub Bot commented on STORM-297:
--------------------------------------
Github user Gvain commented on the pull request:
https://github.com/apache/incubator-storm/pull/103#issuecomment-44635246
Hi, clockfly
1) tps here only consists of spout emitted messages, NOT including acker
messages or any other messages.
3) the network usage is only SINGLE machine network usage, and only the IN
direction bytes counts. And I am using two bonded 1Gb network card.
4) max.spout.pending is 1000.
As for 2), i didn't really stats message latency. All i did is compared the
emitted count by spouts and the received count by bolts, they are quite catch
up with each other
> 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)
