2013
DOI: 10.1016/j.future.2011.05.026
|View full text |Cite
|
Sign up to set email alerts
|

Design and implementation of GXP make — A workflow system based on make

Abstract: This paper describes the rational behind designing workflow systems based on the Unix make by showing a number of idioms useful for workflows comprising many tasks. It also demonstrates a specific design and implementation of such a workflow system called GXP make. GXP make supports all the features of GNU make and extends its platforms from single node systems to clusters, clouds, supercomputers, and distributed systems. Interestingly, it is achieved by a very small code base that does not modify GNU make imp… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
10
0

Year Published

2014
2014
2018
2018

Publication Types

Select...
4
3
1

Relationship

3
5

Authors

Journals

citations
Cited by 16 publications
(10 citation statements)
references
References 23 publications
0
10
0
Order By: Relevance
“…Since all these three systems do not provide any language to describe the dependencies of components/jobs, we generally perform each single job using them and leave the creation of the whole workflows to a known workflow engine called GXP Make [2]. GXP Make uses make to describe the workflow and provides the parallelization of tasks across clusters.…”
Section: Text Processing Workflowsmentioning
confidence: 99%
See 1 more Smart Citation
“…Since all these three systems do not provide any language to describe the dependencies of components/jobs, we generally perform each single job using them and leave the creation of the whole workflows to a known workflow engine called GXP Make [2]. GXP Make uses make to describe the workflow and provides the parallelization of tasks across clusters.…”
Section: Text Processing Workflowsmentioning
confidence: 99%
“…Many systems are proposed to execute workflows, including GXP Make [2], Swift [3], Pegasus [4] and Taverna [5]. A workflow is generally a DAG with many data processing tasks and their dependencies.…”
Section: Introductionmentioning
confidence: 99%
“…While our work has been carried out using the IPS framework's many-task computing environment, the same approach could, at least in principle, be implemented in any many-task environment with the capability to express dependencies among tasks. Relying on literature reports, it appears that many of the frameworks previously discussed in a many-task context could express a dependency-driven formulation of parareal, including Uintah [17], Kepler [15], Taverna [20], Triana [4], GXP Make [25], Swift [27], Pegasus [6], Nephele [26], and PLASMA [24] however such publications rarely provide sufficient detail to determine whether, and how effectively, the system can handle the dynamic nature of the dependency-driven parareal, including convergence rates that can vary significantly by slice, or the more complex "windowed" variant of the algorithm described in Sec. 6.…”
Section: Related Workmentioning
confidence: 99%
“…In addition, as data are stored in files, it is tedious to select a subset of data due to the difficulties in creating index on data. Nowadays, many systems are proposed to execute workflows, including GXP Make [4], Swift [5] and Taverna [6].…”
Section: Introductionmentioning
confidence: 99%