2012
DOI: 10.1145/2426642.2259014
|View full text |Cite
|
Sign up to set email alerts
|

Identifying the sources of cache misses in Java programs without relying on hardware counters

Abstract: Cache miss stalls are one of the major sources of performance bottlenecks for multicore processors. A Hardware Performance Monitor (HPM) in the processor is useful for locating the cache misses, but is rarely used in the real world for various reasons. It would be better to find a simple approach to locate the sources of cache misses and apply runtime optimizations without relying on an HPM. This paper shows that pointer dereferencing in hot loops is a major source of cache misses in Java programs. Based on th… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

1
4
0

Year Published

2014
2014
2021
2021

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(5 citation statements)
references
References 28 publications
1
4
0
Order By: Relevance
“…Figure 10 shows the L2 and L3 Load Cache Misses Per Kilo Instruction (LCMPKI) for both configurations. As shown, the majority of the Dacapo benchmarks are not cache-missintensive, which corresponds with the previous findings [45]. Figure 13.…”
Section: A Characterization Of the Dacapo Benchmarkssupporting
confidence: 90%
“…Figure 10 shows the L2 and L3 Load Cache Misses Per Kilo Instruction (LCMPKI) for both configurations. As shown, the majority of the Dacapo benchmarks are not cache-missintensive, which corresponds with the previous findings [45]. Figure 13.…”
Section: A Characterization Of the Dacapo Benchmarkssupporting
confidence: 90%
“…Adaption of managed runtime There are a few works related to the management of hybrid memory particularly for managed applications [21][22][23][24][25][26]. Shuichi Oikawa's group conduct some preliminary work [21][22][23][24].…”
Section: Related Workmentioning
confidence: 99%
“…Besides, the process could result in a non-trivial execution overhead. Inoue et al [25] identify a code pattern in Java applications that can easily causing L1 and L2 cache misses. However, we find the number of memory accesses caused by this pattern is negligible.…”
Section: Related Workmentioning
confidence: 99%
“…Inoue and Nakatani [36] identify code patterns in Java applications that can cause cache misses in L1 and L2. Gao et al [31] propose a framework including support from hardware, the OS, and the runtime to extend NVM's lifetime.…”
Section: Related Workmentioning
confidence: 99%