2021 ACM/IEEE 48th Annual International Symposium on Computer Architecture (ISCA) 2021
DOI: 10.1109/isca52012.2021.00063
|View full text |Cite
|
Sign up to set email alerts
|

Ripple: Profile-Guided Instruction Cache Replacement for Data Center Applications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
6
1

Relationship

1
6

Authors

Journals

citations
Cited by 15 publications
(7 citation statements)
references
References 72 publications
0
7
0
Order By: Relevance
“…Prior work from Google and Facebook shows that their widely-deployed data center applications lose more than 15% of all pipeline slots due to frontend stalls [25,27,67,133]. As these applications are proprietary, we use the applications used by prior work [75,77,78,86,100,138,150], where frontend stalls are similarly frequent (more than 15%) due to large instruction footprints. These applications include cassandra [2], kafka [3], and tomcat [4] from the Java DaCapo benchmark suite [31], drupal [142], wordpress [144], and mediawiki [143] from Facebook's OSS -performance benchmark suite [16], finagle-chirper and finagle-http [12] from the Java Renaissance benchmark suite [114], clang [6] while building LLVM [85], PostgreSQL [10] while serving pgbench [9] queries, Python [14] while running the pyperformance [11] benchmark suite, MySQL [146] while serving TPC-C queries [35], and verilator [13] while emulating the Rocket Chip [7].…”
Section: Experimental Methodologymentioning
confidence: 99%
See 3 more Smart Citations
“…Prior work from Google and Facebook shows that their widely-deployed data center applications lose more than 15% of all pipeline slots due to frontend stalls [25,27,67,133]. As these applications are proprietary, we use the applications used by prior work [75,77,78,86,100,138,150], where frontend stalls are similarly frequent (more than 15%) due to large instruction footprints. These applications include cassandra [2], kafka [3], and tomcat [4] from the Java DaCapo benchmark suite [31], drupal [142], wordpress [144], and mediawiki [143] from Facebook's OSS -performance benchmark suite [16], finagle-chirper and finagle-http [12] from the Java Renaissance benchmark suite [114], clang [6] while building LLVM [85], PostgreSQL [10] while serving pgbench [9] queries, Python [14] while running the pyperformance [11] benchmark suite, MySQL [146] while serving TPC-C queries [35], and verilator [13] while emulating the Rocket Chip [7].…”
Section: Experimental Methodologymentioning
confidence: 99%
“…As shown, none of the 13 applications we study significantly benefit from these existing replacement policies. Specifically, the state-of-the-art BTB replacement policy, GHRP does not perform well for applications with large working sets [78].…”
Section: Why Do Prior Replacement Policies Fall Short?mentioning
confidence: 99%
See 2 more Smart Citations
“…For the last-level cache(LLC), [3] devised an extra storage based on the LRU policy, to represent the set-dueling counters and insertion and promotion vectors(IPVs), which achieves a weighted speedup of 6.2% over the LRU. In [4], an I-Cache (instruction cache) replacement algorithm is proposed based on the data center application mode that applies the idea of combining the replacement algorithm with instruction prefetching; it is implemented by software. Across different prefetching configurations, this method can avoid up to 53% of I-Cache misses.…”
Section: Introductionmentioning
confidence: 99%