SC18: International Conference for High Performance Computing, Networking, Storage and Analysis 2018
DOI: 10.1109/sc.2018.00037
|View full text |Cite
|
Sign up to set email alerts
|

Dynamic Tracing: Memoization of Task Graphs for Dynamic Task-Based Runtimes

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
8
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
4
4

Relationship

1
7

Authors

Journals

citations
Cited by 17 publications
(8 citation statements)
references
References 21 publications
0
8
0
Order By: Relevance
“…Both LB and WS approaches have their advantages. Notably, WS is often applied in task-parallel Runtime Systems (RTSs) [14], and shared memory scenarios [15,16] (even though it is distributed in nature), although it has been used for highly unpredictable applications in distributed memory as well [17].…”
Section: Related Workmentioning
confidence: 99%
“…Both LB and WS approaches have their advantages. Notably, WS is often applied in task-parallel Runtime Systems (RTSs) [14], and shared memory scenarios [15,16] (even though it is distributed in nature), although it has been used for highly unpredictable applications in distributed memory as well [17].…”
Section: Related Workmentioning
confidence: 99%
“…Dynamic traces have seen some limited use as an extension to JIT. If kernels are labeled in advance, a minimal dynamic trace that primarily stores address information can be used to detect dependencies [21]. This currently relies upon having the kernel labels available in advance, and without this information.…”
Section: Background and Motivationmentioning
confidence: 99%
“…TPS results are difficult to interpret and apply, because efficiency (and thus the amount of useful work) is not constrained. With empty tasks [28], the resulting upper bound on task scheduling throughput fails to represent useful work within a realistic application. With non-empty tasks, since the efficiency of the overall application is typically not reported [3,6], TPS is not a measurement of runtime-limited performance.…”
Section: Metgmentioning
confidence: 99%
“…Intuitively, for a given workload, METG(50%) is the smallest task granularity that maintains at least 50% efficiency, meaning that the application achieves at least 50% of the highest performance (in FLOP/s, B/s, or other application-specific measure) achieved on a given machine. The efficiency bound in METG is a key innovation over previous approaches, such as tasks per second (TPS), that fail to consider the amount of useful work performed (if tasks are non-empty [3,6]) or to perform useful work at all (if tasks are empty [28]).…”
Section: Introductionmentioning
confidence: 99%