[
https://issues.apache.org/jira/browse/STORM-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003396#comment-14003396
]
ASF GitHub Bot commented on STORM-297:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/incubator-storm/pull/103#issuecomment-43636831
Running the unit tests I ran into some errors in
backtype.storm.messaging.netty-unit-test (there were 3 failures like this one)
It looks like you need to update the test to set Config.TOPOLOGY_WORKERS
before creating the context.
```
expected: nil
actual: java.lang.RuntimeException: Fail to construct messaging plugin
from plugin backtype.storm.messaging.netty.Context
at backtype.storm.messaging.TransportFactory.makeContext
(TransportFactory.java:53)
backtype.storm.messaging.netty_unit_test/fn (netty_unit_test.clj:109)
clojure.test$test_var$fn__6926.invoke (test.clj:701)
clojure.test$test_var.invoke (test.clj:701)
clojure.test$test_all_vars$fn__6930$fn__6937.invoke (test.clj:717)
clojure.test$default_fixture.invoke (test.clj:671)
clojure.test$test_all_vars$fn__6930.invoke (test.clj:717)
...
Caused by: java.lang.IllegalArgumentException: Don't know how to
convert null + to int
at backtype.storm.utils.Utils.getInt (Utils.java:308)
backtype.storm.messaging.netty.Context.prepare (Context.java:66)
backtype.storm.messaging.TransportFactory.makeContext
(TransportFactory.java:45)
backtype.storm.messaging.netty_unit_test/fn (netty_unit_test.clj:109)
clojure.test$test_var$fn__6926.invoke (test.clj:701)
clojure.test$test_var.invoke (test.clj:701)
clojure.test$test_all_vars$fn__6930$fn__6937.invoke (test.clj:717)
clojure.test$default_fixture.invoke (test.clj:671)
clojure.test$test_all_vars$fn__6930.invoke (test.clj:717)
clojure.test$default_fixture.invoke (test.clj:671)
```
> 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)
