2010
DOI: 10.1016/j.peva.2010.08.004
|View full text |Cite
|
Sign up to set email alerts
|

Generalized ERSS tree model: Revisiting working sets

Abstract: Accurately characterizing the resource usage of an application at various levels in the memory hierarchy has been a long-standing research problem. Existing characterization studies are either motivated by specific allocation problems (e.g., memory page allocation) or they characterize a specific memory resource (e.g., L2 cache). The studies thus far have also implicitly assumed that there is no contention for the resource under consideration. The inevitable future of virtualization driven consolidation necess… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
6
0

Year Published

2011
2011
2015
2015

Publication Types

Select...
5

Relationship

2
3

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 33 publications
0
6
0
Order By: Relevance
“…Hypervisors, upon the direction of the autonomic manager, control the storage performance of individual VMs by increasing or decreasing the cache space assigned to each VM to meet administrator goals. Further, unlike previous solutions for CPU caches that continuously repartition the cache [40], SSD cache partitions in Centaur are only periodically resized by the global scheduler to adapt to stable changes in the workloads and the storage system [21], [35]. Doing so ensures that stable workload characteristics are reflected post-repartitioning.…”
Section: Centaur Overviewmentioning
confidence: 99%
“…Hypervisors, upon the direction of the autonomic manager, control the storage performance of individual VMs by increasing or decreasing the cache space assigned to each VM to meet administrator goals. Further, unlike previous solutions for CPU caches that continuously repartition the cache [40], SSD cache partitions in Centaur are only periodically resized by the global scheduler to adapt to stable changes in the workloads and the storage system [21], [35]. Doing so ensures that stable workload characteristics are reflected post-repartitioning.…”
Section: Centaur Overviewmentioning
confidence: 99%
“…This is related to the issue of program phases discussed later. The other is skewed popularity, in which some memory locations are much more popular than others, implying that they are reused much more often [380,217,410] (recall Figure 9.8).…”
Section: Memory Behaviormentioning
confidence: 99%
“…Phases may actually be nested, with a major phase of the computation including several subphases, which may also be repeated [455,410]. In addition, one must distinguish between the reuse set, which is those elements that are indeed reused extensively (i, lenA, and lenB in the earlier example), and the other elements, which are transient in nature [216,410]. The reuse set provides a better approximation of the actual memory capacity needed by the application, because the memory used to store transient elements can be reused.…”
Section: Memory Behaviormentioning
confidence: 99%
See 1 more Smart Citation
“…In a companion paper [13], we propose a unified model called the Generalized ERSS Tree Model that comprehensively characterizes working sets across all phases of an application. The core of the model is a metric called effective reuse set size (ERSS) that accurately captures the amount of cache required by an application in a phase to avoid capacity misses.…”
Section: Introductionmentioning
confidence: 99%