[
https://issues.apache.org/jira/browse/STORM-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946420#comment-15946420
]
Roshan Naik commented on STORM-2284:
------------------------------------
Hmm... i think this will need some more thought into how that changes would be
needed to the scheduler / elsewhere.
I am thinking .. each supervisor would need to know how many cores it is
managing.. and each new worker gets assigned unused cores. At submit time, need
to figure out where each spout and bolt instance goes... based on the groupings
used.
Ya I/O threads over allocation is reasonable... we have two types of IO :
outbound & inbound. Hard to say without experimenting and would depend on
throughput being sustained....but perhaps the outbound threads could be pinned
to same core.. and inbound threads to another core.
If we decide to do memory mapped Queues for intra host messaging, then we have
inter-host I/O and intra-host I/O... each with in/bound variations.
> Storm Worker Redesign
> ---------------------
>
> Key: STORM-2284
> URL: https://issues.apache.org/jira/browse/STORM-2284
> Project: Apache Storm
> Issue Type: Umbrella
> Components: storm-core
> Affects Versions: 2.0.0
> Reporter: Roshan Naik
> Assignee: Roshan Naik
>
> Much has been learnt from evolving the 1.x line. We can now use the benefit
> of hindsight and apply these learnings into the future work on 2.x line.
> The goal is to rethink the Worker to improve performance, enhance its
> abilities and also retain compatibility.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
