You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@reef.apache.org by "John Yang (JIRA)" <ji...@apache.org> on 2015/08/27 15:44:47 UTC

[jira] [Assigned] (REEF-518) Smarter VortexWorker-Tasklet scheduling

     [ https://issues.apache.org/jira/browse/REEF-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Yang reassigned REEF-518:
------------------------------

    Assignee: John Yang

> Smarter VortexWorker-Tasklet scheduling
> ---------------------------------------
>
>                 Key: REEF-518
>                 URL: https://issues.apache.org/jira/browse/REEF-518
>             Project: REEF
>          Issue Type: Sub-task
>          Components: Vortex
>            Reporter: John Yang
>            Assignee: John Yang
>            Priority: Minor
>
> Currently Vortex uses an embedded random VortexWorker-Tasklet scheduling algorithm.
> Once we have better understanding of key metrics(e.g. resource reliability, queue size, data locality) for making scheduling decisions we can optimize the algorithm and even make a pluggable interface for it.
> For example we can maintain data structures in a way that enables fast scheduling using indices on those metrics.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)