Proceedings of the 2021 ACM SIGPLAN International Symposium on Memory Management 2021
DOI: 10.1145/3459898.3463907
|View full text |Cite
|
Sign up to set email alerts
|

Radiant: efficient page table management for tiered memory systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2022
2022
2023
2023

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(5 citation statements)
references
References 26 publications
0
5
0
Order By: Relevance
“…We choose eight representative memoryintensive applications, including graph processing (Graph500, PageRank), an HPC workload (XSBench), machine learning (Liblinear), an in-memory database engine (Silo), an in-memory index lookup (Btree), and SPEC CPU 2017 (603.bwaves, 654.roms). These benchmarks are widely used to evaluate tiered memory systems [36,68], huge page management [26,38,57,67], and large memory servers [2,5,56]. Note that we choose only two benchmarks from SPEC CPU 2017 since they are the only ones that consume more than 10GB memory.…”
Section: Evaluation Methodologymentioning
confidence: 99%
See 1 more Smart Citation
“…We choose eight representative memoryintensive applications, including graph processing (Graph500, PageRank), an HPC workload (XSBench), machine learning (Liblinear), an in-memory database engine (Silo), an in-memory index lookup (Btree), and SPEC CPU 2017 (603.bwaves, 654.roms). These benchmarks are widely used to evaluate tiered memory systems [36,68], huge page management [26,38,57,67], and large memory servers [2,5,56]. Note that we choose only two benchmarks from SPEC CPU 2017 since they are the only ones that consume more than 10GB memory.…”
Section: Evaluation Methodologymentioning
confidence: 99%
“…Software-based tiered memory system. Prior softwarecontrolled tiered memory systems have explored the design space in various aspects including page migration [34,71,83,84], hotness detection [4,15,41], page replacement [28,48], and kernel object tiering [31,36] at different layers such as the application [29,44,69,79], library [21,54,68], and OS [14,27,30,32,76,78]. HotBox [14] suggests not using huge pages in tiered memory systems due to the hotness fragmentation in huge pages.…”
Section: Related Workmentioning
confidence: 99%
“…To understand whether these benefits hold in a disaggregated memory system, we pin the working set entirely in remote memory and configure the system to use huge pages. Page tables are placed in local memory for the best performance [6,29]. We compare huge and base page performance under varying remote memory latencies.…”
Section: Slow Remote Memory Renders Huge Pages Ineffectivementioning
confidence: 99%
“…Memory accesses triggered by page walks can account for up to 20∼40% of total memory accesses [20]. Recent studies have pointed out that address translations requiring many memory accesses are the primary performance bottleneck [18], [29], [30], [33], [34], [42], [43].…”
Section: Emerging Workload Challengesmentioning
confidence: 99%
“…However, L2 TLB does not perform well on workloads with large memory footprints and irregular memory access patterns (bc-kron, bc-urand, bfs-kron, bfs-urand, and gups), and hence these workloads suffer from frequent L2 TLB misses. Due to the frequent misses on the L2 TLB, the fraction of page walks in total memory access latency becomes considerably high when these workloads are executed, resulting in a substantial decrease in system performance [15], [43], [44].…”
Section: Motivation a Tlb Missesmentioning
confidence: 99%