2014
DOI: 10.14529/jsfi140204
|View full text |Cite
|
Sign up to set email alerts
|

Energy, Memory, and Runtime Tradeoffs for Implementing Collective Communication Operations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2015
2015
2024
2024

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 15 publications
(1 citation statement)
references
References 51 publications
(55 reference statements)
0
1
0
Order By: Relevance
“…The approaches that target the Message Passing Interface (MPI) applications mainly involve mitigation of workload imbalance between the process (slack) [4,16,29,41]. Other MPI-centric solutions address cases where the processor cores wait on the memory or network [5,22,26,43,48,49]. Concurrency throttling has been widely used by adapting the thread count in OpenMP programs that are memory-constrained to reduce power consumption [12,13,31,37].…”
Section: Related Workmentioning
confidence: 99%
“…The approaches that target the Message Passing Interface (MPI) applications mainly involve mitigation of workload imbalance between the process (slack) [4,16,29,41]. Other MPI-centric solutions address cases where the processor cores wait on the memory or network [5,22,26,43,48,49]. Concurrency throttling has been widely used by adapting the thread count in OpenMP programs that are memory-constrained to reduce power consumption [12,13,31,37].…”
Section: Related Workmentioning
confidence: 99%