2009 IEEE International Symposium on Parallel &Amp; Distributed Processing 2009
DOI: 10.1109/ipdps.2009.5161045
|View full text |Cite
|
Sign up to set email alerts
|

Efficient scheduling of task graph collections on heterogeneous resources

Abstract: In this paper, we focus on scheduling jobs on computing Grids. In our model, a Grid job is made of a large collection of input data sets, which must all be processed by the same task graph or workflow, thus resulting in a collection of task graphs problem. We are looking for a competitive scheduling algorithm not requiring complex control. We thus only consider single-allocation strategies. In addition to a mixed linear programming approach to find an optimal allocation, we present different heuristic schemes.… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
39
0

Year Published

2010
2010
2018
2018

Publication Types

Select...
4
2
2

Relationship

2
6

Authors

Journals

citations
Cited by 14 publications
(39 citation statements)
references
References 22 publications
0
39
0
Order By: Relevance
“…This must be done in a way that respects the precedence constraints among tasks. An efficient schedule is one that minimizes the total execution time, or the schedule length, of the parallel application [15][16][17][18][19][20][21][22][23]. www.ijacsa.thesai.org…”
Section: Problem Definitionmentioning
confidence: 99%
“…This must be done in a way that respects the precedence constraints among tasks. An efficient schedule is one that minimizes the total execution time, or the schedule length, of the parallel application [15][16][17][18][19][20][21][22][23]. www.ijacsa.thesai.org…”
Section: Problem Definitionmentioning
confidence: 99%
“…Iverson and Özgüner [10] propose an approach to minimize the average makespan in a heterogeneous environment with a Poisson arrival process of DAG-type workflows. Gallet et al [11] aim at maximizing the throughput, which corresponds to minimizing the response time in our formulation. However, theirs is an offline deployment algorithm, therefore the same for all workflow instances, and assumes deterministic task processing and communication times.…”
Section: Introductionmentioning
confidence: 99%
“…It does this by considering the ratio between the code size of the tasks and the amount of data that is needed by the tasks. Data-intensive tasks [3] will be scheduled in a data-driven manner and code-intensive tasks [3] will be scheduled in a code-driven manner.…”
Section: Introductionmentioning
confidence: 99%