2013 IEEE International Symposium on Workload Characterization (IISWC) 2013
DOI: 10.1109/iiswc.2013.6704667
|View full text |Cite
|
Sign up to set email alerts
|

iBench: Quantifying interference for datacenter applications

Abstract: Abstract-Interference between co-scheduled applications is one of the major reasons that causes modern datacenters (DCs) to operate at low utilization. DC operators traditionally sidestep interference either by disallowing colocation altogether and providing isolated server instances, or by requiring the users to express resource reservations, which are often exaggerated to counter-balance the unpredictability in the quality of allocated resources. Understanding, reducing and managing interference can signific… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
43
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
4
3
2

Relationship

1
8

Authors

Journals

citations
Cited by 110 publications
(43 citation statements)
references
References 32 publications
0
43
0
Order By: Relevance
“…AutoPro uses a PI controller to asymptotically close this gap and can work with any metric (eg, frame/s) as long as developers can provide it. Delimitrou and Kozyrakis [13] proposed iBench to inject/run a series of 15 snippets into a VM to pressure its running application and identify the amount of contention it can tolerate before violating its QoS.…”
Section: Agent Based Approachesmentioning
confidence: 99%
See 1 more Smart Citation
“…AutoPro uses a PI controller to asymptotically close this gap and can work with any metric (eg, frame/s) as long as developers can provide it. Delimitrou and Kozyrakis [13] proposed iBench to inject/run a series of 15 snippets into a VM to pressure its running application and identify the amount of contention it can tolerate before violating its QoS.…”
Section: Agent Based Approachesmentioning
confidence: 99%
“…vmDataCollector(vmName,startTime,finishTime) collects/records performance of a VM under imposed limitations through polling several Hypervisor level metrics (eg, CPU utilization): it neither demands nor needs any specific metric from the VM itself. This makes vmBBProfiler unique when compared with many other similar approaches that either ask developers to provide specific metrics to reflect a VM's performance [5,6,8,[11][12][13]21], or use peripheral systems to collect external metrics to reflect such performance [24]. Because, the vmBBProfiler remains fully agnostic to the actual internal processes of a VM, we refer to our approach as a 'Black-Box' technique.…”
Section: Architecture Of Vmbbprofilermentioning
confidence: 99%
“…Interfering Workload: Interfering workload anomalies are the major cause of performance degradation in data centers (DC) [17]. Interfering workload anomalies results from competition for resources and occur due to various reasons; as simple as unannounced maintenance on a cluster (e.g., security scans), or a storage array that is performing a system operation such as replication and RAID construction.…”
Section: ) Anomaliesmentioning
confidence: 99%
“…RU quality: The utility an application can extract from an RU depends on the hardware type (e.g., 2 GHz vs 3 GHz core) and the interference on shared resources from other jobs on the same server. The scheduler [12,13] obtains the interference preferences of an incoming job using a small set of microbenchmarks to inject pressure of increasing intensity (from 0 to 99%) on one of ten shared resources of interest [11]. Interference preferences capture, first, the amount of pressure t i a job can tolerate in each shared resource i ∈ [1, N ], and second, the amount of pressure c i it itself will generate in that resource.…”
Section: Analytical Frameworkmentioning
confidence: 99%