2021
DOI: 10.1109/tpds.2020.3015148
|View full text |Cite
|
Sign up to set email alerts
|

Multi-GPU Parallelization of the NAS Multi-Zone Parallel Benchmarks

Abstract: GPU-based computing systems have become a widely accepted solution for the high-performance-computing (HPC) domain. GPUs have shown highly competitive performance-per-watt ratios and can exploit an astonishing level of parallelism. However, exploiting the peak performance of such devices is a challenge, mainly due to the combination of two essential aspects of multi-GPU execution. On one hand, the workload should be distributed evenly among the GPUs. On the other hand, communications between GPU devices are co… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2023
2023
2024
2024

Publication Types

Select...
2

Relationship

1
1

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 21 publications
0
1
0
Order By: Relevance
“…The basis for the performance evaluation is the comparison between four versions of the benchmarks in the suite: GPU-based and CPU-based non-hybrid versions already studied in previous studies for the NPB-MZ benchmark suite (Duran et al 2005; Gonzalez and Morancho 2020; González and Morancho 2021) and two hybrid executions under two work-distribution schemes. On the one hand, a static scheduling that corresponds to the default and only supported scheduling for hybrid executions in the latest OpenMP specification (OpenMP 5.2).…”
Section: Discussionmentioning
confidence: 99%
“…The basis for the performance evaluation is the comparison between four versions of the benchmarks in the suite: GPU-based and CPU-based non-hybrid versions already studied in previous studies for the NPB-MZ benchmark suite (Duran et al 2005; Gonzalez and Morancho 2020; González and Morancho 2021) and two hybrid executions under two work-distribution schemes. On the one hand, a static scheduling that corresponds to the default and only supported scheduling for hybrid executions in the latest OpenMP specification (OpenMP 5.2).…”
Section: Discussionmentioning
confidence: 99%