2018
DOI: 10.1155/2018/2068490
|View full text |Cite
|
Sign up to set email alerts
|

Topology-Aware Strategy for MPI-IO Operations in Clusters

Abstract: This paper presents the topology-aware two-phase I/O (TATP), which optimizes the most popular collective MPI-IO implementation of ROMIO. In order to improve the hop-bytes metric during the file access, topology-aware two-phase I/O employs the Linear Assignment Problem (LAP) for finding an optimal assignment of file domain to aggregators, an aspect which is not considered in most two-phase I/O implementations. The distribution is based on the local data stored by each process, and its main purpose is to reduce … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2020
2020
2020
2020

Publication Types

Select...
2
1

Relationship

1
2

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 19 publications
(21 reference statements)
0
2
0
Order By: Relevance
“…The topology aware algorithm (TA-Two-Phase I/O) takes the I/O pattern and network topology into consideration when assigning file domains to aggregators [17]. It tries to schedule the inter-process communications to the low levels of the tapered hierarchical networks.…”
Section: Topology Aware Algorithm For Two-phase I/o (Ta-two-phase mentioning
confidence: 99%
“…The topology aware algorithm (TA-Two-Phase I/O) takes the I/O pattern and network topology into consideration when assigning file domains to aggregators [17]. It tries to schedule the inter-process communications to the low levels of the tapered hierarchical networks.…”
Section: Topology Aware Algorithm For Two-phase I/o (Ta-two-phase mentioning
confidence: 99%
“…The scope of techniques used will be very huge, including checkpoint-prelaunch variations dependent on uncoordinated replication of rollback recovery, fault tolerance based on algorithms where mathematical properties are leveraged to escape checkpoints Another common characteristic found in most of these advanced methods for recovery of failure, as compared to traditional rollback recovery where the entire machine is used the program is expected to continue running despite processor failures, minimizing the I / O, downtime and overhead losses incurred [6]. The MPI Standard does not, however, Nevertheless, once affected, the MPI Standard does not specify the exact actions of MPI implementations, by failures.…”
Section: Introductionmentioning
confidence: 99%