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

Using Differential Execution Analysis to Identify Thread Interference

Abstract: Understanding the performance of a multi-threaded application is difficult. The threads interfere when they access the same shared resource, which slows down their execution. Unfortunately, current profiling tools report the hardware components or the synchronization primitives that saturate, but they cannot tell if the saturation is the cause of a performance bottleneck. In this paper, we propose a holistic metric able to pinpoint the blocks of code that suffer interference the most, regardless of the interfe… 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

2021
2021
2022
2022

Publication Types

Select...
2
2

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(2 citation statements)
references
References 41 publications
0
2
0
Order By: Relevance
“…For example on Densenet, the fastest worker reads samples in 11.9s while the slowest worker reads samples in 142s. This high variation of I/O performance could indicate that the PFS suffers congestion caused by the 512 workers performing IO concurrently [39]. Moreover, workers wait for each other using collective communication during the gradient exchange.…”
Section: F Performancementioning
confidence: 99%
“…For example on Densenet, the fastest worker reads samples in 11.9s while the slowest worker reads samples in 142s. This high variation of I/O performance could indicate that the PFS suffers congestion caused by the 512 workers performing IO concurrently [39]. Moreover, workers wait for each other using collective communication during the gradient exchange.…”
Section: F Performancementioning
confidence: 99%
“…In which, the practical response time is the completed time in the simulation tests, and the theoretical response time is the sum of the arrival time and the required time for doing the read/write request. This metric is referring to Reference [34] and can give the theoretical slowdown of read/write requests caused by waiting in the I/O queue.…”
Section: Long-tail Latencymentioning
confidence: 99%