ITR: Architectural Support for Service Level Agreements

Lebeck对服务级别协议的体系结构支持摘要数据中心构成了当今社会所依赖的基于互联网的计算基础设施的组成部分。从电子商务和网络服务器到用于科学研究的网格计算，各种应用都使用数据中心提供的计算和存储。通过整合包括硬件和系统管理在内的资源，数据中心客户可以减少开支。然而，客户期望数据中心提供合理水平的服务，即使对这些系统提供的服务有不同的需求。为了最大限度地提高所有客户的服务，数据中心可以根据签约的服务级别协议(SLA)为各种应用程序(客户)提供差异化的服务级别。SLA根据商定的指标(例如，性能、可用性、输出带宽、服务器负载)指定要求，并且它们通常包括不同服务级别的几个价格点。不幸的是，对于多线程系统模型(例如，多处理器)，对传统单处理器指标的简单扩展可能会产生误导。所面临的挑战是开发能够弥合底层硬件行为和高层指标之间差距的指标。拟议的研究通过探索包括SLA指标、系统模型、硬件级别指标和实施的设计空间来满足这一需求。该项目将通过同时考虑系统模型和指标的预期用途来制定硬件级别的指标。一旦定义了指标，就可以探索各种硬件实现。已经开发了一个案例研究SLA性能度量和相应的硬件度量，称为每周期关键指令(CIPC)。全系统模拟和商业工作负载的初步结果强化了这样的假设，即指标必须捕获低级硬件的行为。

LebeckArchitectural Support for Service Level AgreementsAbstractData centers comprise an integral part of today's internet-based computing infrastructure upon which society relies. Applications ranging from e-commerce and web servers to grid computing for scientific research use the computation and storage provided by data centers. By consolidating resources, including hardware and system administration, data center customers can reduce expenses. However, customers expect a reasonable level of service from data centers, even with varying demand for the services these systems provide. To maximize service across all customers, a data center can provide differentiated service levels to various applications (customers) based on a contracted Service Level Agreement (SLA).SLAs specify requirements in terms of agreed upon metrics (e.g., performance, availability, output bandwidth, server load), and they usually include several price points for different service levels. Unfortunately, with multithreaded system models (e.g., multiprocessors) simple extensions to conventional uniprocessor metrics can be misleading. The challenge is to develop metrics that bridge the gap between low-level hardware behavior and high-level metrics.The proposed research addresses this need by exploring a design space that includes SLA metrics, system models, hardware-level metrics, and implementations. The project will develop hardware-level metrics by considering both the system model and the intended use of the metric. Once the metric is defined, various hardware implementations can be explored. A case study SLA performance metric and a corresponding hardware metric called Critical Instructions Per Cycle (CIPC) have been developed. Preliminary results with full-system simulation and commercial workloads reinforce the hypothesis that metrics must capture the behavior of low-level hardware.