IEEE International Symposium on Performance Analysis of Systems and Software, 2005. ISPASS 2005. 2005
DOI: 10.1109/ispass.2005.1430578
|View full text |Cite
|
Sign up to set email alerts
|

The Strong correlation Between Code Signatures and Performance

Abstract: A recent study [1]

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
36
0

Year Published

2005
2005
2016
2016

Publication Types

Select...
6
4

Relationship

2
8

Authors

Journals

citations
Cited by 65 publications
(36 citation statements)
references
References 19 publications
0
36
0
Order By: Relevance
“…If the distance between the two BBVs is small (close to 0), then the two intervals spend about the same amount of time in roughly the same code, and therefore we expect the performance of those two intervals to be similar. Code signatures grouped into the same cluster have been shown to exhibit similar CPI, numbers of branch mispredictions, numbers of cache misses, etc [10,14].…”
Section: Simpointmentioning
confidence: 99%
“…If the distance between the two BBVs is small (close to 0), then the two intervals spend about the same amount of time in roughly the same code, and therefore we expect the performance of those two intervals to be similar. Code signatures grouped into the same cluster have been shown to exhibit similar CPI, numbers of branch mispredictions, numbers of cache misses, etc [10,14].…”
Section: Simpointmentioning
confidence: 99%
“…Application runtime, measured in instructions, is on the horizontal axis; the vertical axis represents the offset d. Light colors denote a low similarity between the BBVs at a given point in the program with those a distance d away, whereas dark colors denote strong correlation -which implies similar execution behavior [14]. In this case, we can see that the N-ft benchmark, running the class A input set with 8 threads, has one periodicity at 550k instructions that occurs for a part of the application runtime, and another which occurs at 1.14M instructions and exists during the entire application execution.…”
Section: B Determining Application Periodicitymentioning
confidence: 99%
“…BBV similarity is quantified by computing the Manhattan distance between two BBVs. The intuitive notion is that intervals of execution with similar code signatures have similar architectural behavior, and this has been shown to be the case by Lau et al [21]. Therefore, only one interval from each phase needs to be simulated in order to recreate an accurate picture of the entire program execution.…”
Section: Representative Samplingmentioning
confidence: 99%