[jira] [Comment Edited] (STORM-2284) Storm Worker Redesign

["Ambud Sharma (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STORM-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943640#comment-15943640 ] 

Ambud Sharma edited comment on STORM-2284 at 3/27/17 5:01 PM:
--------------------------------------------------------------

[~roshan_naik] for CPU pining is the idea to create a new scheduler, limit slot calculation based on cores or put a worker level constraint?

For IO oriented tasks overallocation of threads may be reasonable however for CPU / memory bound tasks I agree cache eviction is more critical for performance.

One thought is to start by creation a warning for the topology submitter when overallocation of threads is done.


was (Author: ashar103):
[~roshan_naik] for CPU pining is the idea to create a new scheduler, limit slot calculation based on cores or put a worker level constraint?

> 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)