Workflows for E-Science
DOI: 10.1007/978-1-84628-757-2_22
|View full text |Cite
|
Sign up to set email alerts
|

Workflow Management in Condor

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
84
0
2

Publication Types

Select...
8
2

Relationship

0
10

Authors

Journals

citations
Cited by 123 publications
(89 citation statements)
references
References 14 publications
0
84
0
2
Order By: Relevance
“…WorkflowSim is tightly bound to the SWfMS Pegasus [20] and adds to CloudSim (1) the workflow engine underlying Pegasus and DagMan [41], (2) an elaborate model of node failures, (3) a model of delays occurring in the various levels of the Pegasus stack (e.g., queue delays, pre/post-processing delays, data transfer delays), and (4) the implementations of several workflow schedulers implemented in Pegasus (e.g., greedy task queue, HEFT [23], Min-Min, and Max-Min [24]). Parameters are directly learned from traces of real executions.…”
Section: Related Workmentioning
confidence: 99%
“…WorkflowSim is tightly bound to the SWfMS Pegasus [20] and adds to CloudSim (1) the workflow engine underlying Pegasus and DagMan [41], (2) an elaborate model of node failures, (3) a model of delays occurring in the various levels of the Pegasus stack (e.g., queue delays, pre/post-processing delays, data transfer delays), and (4) the implementations of several workflow schedulers implemented in Pegasus (e.g., greedy task queue, HEFT [23], Min-Min, and Max-Min [24]). Parameters are directly learned from traces of real executions.…”
Section: Related Workmentioning
confidence: 99%
“…Initially, with GPUs in a testing phase, this was accomplished locally at a few sites with DAGMan for HTCondor [8]. This worked fairly reliably, but did not extend to other job submission systems and did not allow jobs from one site to utilize GPUs at another site.…”
Section: Iceprod V1mentioning
confidence: 99%
“…HTTP requests are an example [31]: some resources (e.g., images) are requested only because they are referenced by others (web pages). Job-and task-level workloads are likely to have this flavor, too: users may use higher-level tools (such as [32]- [35]) to write workflows on top of a lower-level scheduler from which the trace is extracted. Unless the obfuscation is done with care, the workflow's dependency information is easy to cull by mistake.…”
Section: A Unavailable Informationmentioning
confidence: 99%