2017
DOI: 10.1002/cpe.4147
|View full text |Cite
|
Sign up to set email alerts
|

In‐memory staging and data‐centric task placement for coupled scientific simulation workflows

Abstract: Coupled scientific simulation workflows are composed of heterogeneous component applications that simulate different aspects of the physical phenomena being modeled and that interact and exchange significant volumes of data at runtime. As the data volumes and generation rates keep growing, the traditional disk I/O-based data movement approach becomes cost prohibitive, and workflow requires more scalable and efficient approach to support the data movement. Moreover, the cost of moving large volume of data over … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
11
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
4
4
1

Relationship

1
8

Authors

Journals

citations
Cited by 16 publications
(11 citation statements)
references
References 30 publications
0
11
0
Order By: Relevance
“…Studying such strategies would be a first step in evaluating the impact of data transfers and network performance on the execution of scientific workflows. We also plan to extend the simulation capacities and realism of Sim-Situ by developing more complex versions of the Data Transport Layer component that mimic the behavior of popular implementations such as DataSpaces [14] or Dimes [15]. The objective is to provide Sim-Situ users with the capacity to select which flavor of the DTL they want to use in the simulation of their in-situ workflows.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Studying such strategies would be a first step in evaluating the impact of data transfers and network performance on the execution of scientific workflows. We also plan to extend the simulation capacities and realism of Sim-Situ by developing more complex versions of the Data Transport Layer component that mimic the behavior of popular implementations such as DataSpaces [14] or Dimes [15]. The objective is to provide Sim-Situ users with the capacity to select which flavor of the DTL they want to use in the simulation of their in-situ workflows.…”
Section: Discussionmentioning
confidence: 99%
“…A SimGrid plugin is a standalone piece of code that composes some of basic concepts exposed by the SimGrid API to offer a higher level of abstraction useful in a specific context. In this paper, the proposed plugin relies on data structures accessed through a Producer-Consumer synchronization mechanism commonly used in actual DTLs [14,15]. Using this plugin only requires to include an extra header file in the application code to use the functions it provides.…”
Section: Sim-situ Architecturementioning
confidence: 99%
“…Among the fifteen in situ processing systems characterized in [2], eleven follow the applicationaware approach, i.e., rely on an API for the integration of analysis/visualization with a numerical simulation. Moreover, five of these systems focus on data movements between components and implement a data transport layer [15]- [19]. As this is considered as the most flexible, extensible, and efficient way to implement in situ processing, we decided to simulate such a DTL in SIM-SITU.…”
Section: Sim-situ Architecturementioning
confidence: 99%
“…Such an in-memory or cross-node data transfer can be made to respect physics constraints (conservation, divergence free conditions, etc.) and is also much more efficient than file I/O based transfers [42][43][44]. This need can be best served with the common low-level data layouts and interfaces as mentioned above and/or by promoting/enabling interoperable mesh/particle capabilities among existing tools in the ecosystem.…”
Section: Software Ecosystem -Interoperability and Policiesmentioning
confidence: 99%