Proceedings of the 2nd Workshop on Many-Task Computing on Grids and Supercomputers 2009
DOI: 10.1145/1646468.1646470
|View full text |Cite
|
Sign up to set email alerts
|

Exploring many task computing in scientific workflows

Abstract: One of the main advantages of using a scientific workflow management system (SWfMS) to orchestrate data flows among scientific activities is to control and register the whole workflow execution. The execution of activities within a workflow with high performance computing (HPC) presents challenges in SWfMS execution control. Current solutions leave the scheduling to the HPC queue system. Since the workflow execution engine does not run on remote clusters, SWfMS are not aware of the parallel strategy of the wor… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
33
0

Year Published

2010
2010
2021
2021

Publication Types

Select...
5
2
2

Relationship

6
3

Authors

Journals

citations
Cited by 28 publications
(33 citation statements)
references
References 31 publications
0
33
0
Order By: Relevance
“…Hydra [17] is a middleware that provides a set of components to be included on the workflow specification of any SWfMS to control parallelism of activities following the MTC paradigm. Hydra is based on a homogeneous cluster environment and relies on a centralized scheduler (such as Torque [18]).…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…Hydra [17] is a middleware that provides a set of components to be included on the workflow specification of any SWfMS to control parallelism of activities following the MTC paradigm. Hydra is based on a homogeneous cluster environment and relies on a centralized scheduler (such as Torque [18]).…”
Section: Introductionmentioning
confidence: 99%
“…Using Hydra, the MTC parallelism strategy can be registered, reused, and provenance may be uniformly gathered during the execution of workflows. In previous work [17,19], parameter sweep mechanisms were developed and explored using Hydra. However, Hydra still lacks on data parallelism mechanisms coupled to provenance facilities.…”
Section: Introductionmentioning
confidence: 99%
“…After this filter, the number of workflows was reduced to 36 workflows (C 36 2 = 630 comparisons). The machine in which SimiFlow was executed using Hydra middleware (Ogasawara et al 2009a) is the SGI Altix ICE 8200 with 64 nodes (Intel Xeon 8-core processor). The experiment used four nodes (32 cores).…”
Section: Resultsmentioning
confidence: 99%
“…Even though the workflow execution log could be browsed, this is far from provenance data query. Our previous works in supporting workflow scientists from bioinformatics [12] and numerical methods [13] have led us to develop services to query provenance data during the execution [14]. We define this type of provenance as runtime provenance data.…”
Section: Introductionmentioning
confidence: 99%