Swinburne
Browse

Do we need to handle every temporal violation in scientific workflow systems?

Download (1.55 MB)
journal contribution
posted on 2024-07-26, 14:01 authored by Xiao Liu, Yun YangYun Yang, Dong Yuan, Jue Chen
Scientific processes are usually time constrained with overall deadlines and local milestones. In scientific workflow systems, due to the dynamic nature of the underlying computing infrastructures such as grid and cloud, execution delays often take place and result in a large number of temporal violations. Temporal violation handling is to execute violation handling strategies which can compensate for the occurring time deficit but would impose some additional cost. Generally speaking, the two fundamental requirements for delivering satisfactory temporal QoS in scientific workflow systems are temporal conformance and cost effectiveness. Every task for workflow temporal management incurs some cost. Take a single temporal violation handling as an example, its cost can be primarily referred to monetary costs and time overheads of violation handling strategies which are normally nontrivial in scientific workflow systems.

Funding

Novel cloud computing based workflow technology for managing large numbers of process instances

Australian Research Council

Find out more...

Cost effective storage of massive intermediate data in cloud computing applications

Australian Research Council

Find out more...

History

Available versions

PDF (Accepted manuscript)

ISSN

1049-331X

Journal title

ACM Transactions on Software Engineering and Methodology

Volume

23

Issue

1

Pagination

33 pp

Publisher

ACM

Copyright statement

Copyright © 2014 ACM. This the accepted manuscript of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version was published in ACM Transactions on Software Engineering and Methodology,vol. 23, iss. 1,(Feb 2014), pp. 5.2-5.34, http://doi.org/10.1145/2559938

Language

eng

Usage metrics

    Publications

    Categories

    No categories selected

    Keywords

    Exports

    RefWorks
    BibTeX
    Ref. manager
    Endnote
    DataCite
    NLM
    DC