Copyright © 2005 Elsevier B.V. All rights reserved.
Received 29 June 2004;
References and further reading may be available for this article. To view references and further reading you must purchase this article.
Abstract
As more business applications have become web enabled, the web server architecture has evolved to provide performance isolation, service differentiation, and QoS guarantees. Various server mechanisms that provide QoS extensions, however, rely on external administrators to set the right parameter values for their desirable performance. Due to the complexity of handling varying workloads and bursty traffic, configuring such parameters optimally becomes a challenge. In this paper, we describe an observation-based approach for self-managing web servers that can adapt to changing workloads while maintaining the QoS requirements of different classes. In this approach, the system state is monitored continuously and parameter values of various system resources—primarily the accept queue and the CPU—are adjusted to maintain the system-wide QoS goals. We implement our techniques using the Apache web server and the Linux operating system. We first demonstrate the need to manage different resources in the system depending on the workload characteristics. We then experimentally demonstrate that our observation-based system monitors such as workload changes and adjusts the resource parameters of the accept queue and CPU schedulers in order to maintain the QoS requirements of the different classes.
Keywords: Web server; Self-managing; Dynamic resource allocation
Article Outline
- 1. Introduction
- 1.1. Motivation
- 1.2. Research contributions
- 2. Analyzing the bottlenecks in web request processing
- 3. Adaptive QoS architecture
- 3.1. SYN classifier
- 3.2. Accept queue scheduler
- 3.3. CPU scheduler
- 3.4. Monitoring framework
- 4. Adaptation engine
- 5. Experimental evaluation
- 5.1. Experimental testbed
- 5.2. CPU adaptation
- 5.3. Accept queue adaptation
- 5.4. System-wide adaptation
- 6. Related work
- 7. Conclusions and future work
- References






E-mail Article
Add to my Quick Links

Cited By in Scopus (1)







