Resource pool management: Reactive versus proactive or let’s be friends

• Published in: Computer networks (Amsterdam, Netherlands : 1999) Vol. 53; no. 17; pp. 2905 - 2922
• Main Authors: Gmach, Daniel, Rolia, Jerry, Cherkasova, Ludmila, Kemper, Alfons
• Format: Journal Article
• Language: English
• Published: Amsterdam Elsevier B.V 03.12.2009; Elsevier Sequoia S.A
• Subjects: Comparative analysis; Controllers; Enterprise workload analysis; Integrated approach; Quality of service; Resource pool management; Simulation; Studies; Virtualized data centres; Workloads; Virtualized data centres; Resource pool management; Enterprise workload analysis; Simulation
• ISSN: 1389-1286; 1872-7069
• DOI: 10.1016/j.comnet.2009.08.011

The consolidation of multiple workloads and servers enables the efficient use of server and power resources in shared resource pools. We employ a trace-based workload placement controller that uses historical information to periodically and proactively reassign workloads to servers subject to their quality of service objectives. A reactive migration controller is introduced that detects server overload and underload conditions. It initiates the migration of workloads when the demand for resources exceeds supply. Furthermore, it dynamically adds and removes servers to maintain a balance of supply and demand for capacity while minimizing power usage. A host load simulation environment is used to evaluate several different management policies for the controllers in a time effective manner. A case study involving three months of data for 138 SAP applications compares three integrated controller approaches with the use of each controller separately. The study considers trade-offs between: (i) required capacity and power usage, (ii) resource access quality of service for CPU and memory resources, and (iii) the number of migrations. Our study sheds light on the question of whether a reactive controller or proactive workload placement controller alone is adequate for resource pool management. The results show that the most tightly integrated controller approach offers the best results in terms of capacity and quality but requires more migrations per hour than the other strategies.