You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Byung-Gon Chun (JIRA)" <ji...@apache.org> on 2015/08/30 05:50:45 UTC
[jira] [Updated] (REEF-518) Smarter VortexWorker-Tasklet scheduling
[ https://issues.apache.org/jira/browse/REEF-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Byung-Gon Chun updated REEF-518:
--------------------------------
Fix Version/s: 0.13
> 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
> Fix For: 0.13
>
>
> 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)