Multiple-resource request scheduling for differentiated QoS at website gateway

  • Authors:

  • Ying-Dar Lin;Ching-Ming Tien;Shih-Chiang Tsao;Ruo-Hua Feng;Yuan-Cheng Lai

  • Affiliations:

  • National Chiao Tung University, Department of Computer Science, Room 701, EIC Building, 1001 Ta Hsueh Road, Hsinchu 300, Taiwan;National Chiao Tung University, Department of Computer Science, Room 701, EIC Building, 1001 Ta Hsueh Road, Hsinchu 300, Taiwan;National Chiao Tung University, Department of Computer Science, Room 701, EIC Building, 1001 Ta Hsueh Road, Hsinchu 300, Taiwan;National Chiao Tung University, Department of Computer Science, Room 701, EIC Building, 1001 Ta Hsueh Road, Hsinchu 300, Taiwan;National Chiao Tung University, Department of Computer Science, Room 701, EIC Building, 1001 Ta Hsueh Road, Hsinchu 300, Taiwan

  • Venue:
  • Computer Communications
  • Year:
  • 2008

Quantified Score

Hi-index 0.24

Visualization

Abstract

Differentiated quality of service is a way for a website operator to provide different service levels to its clients. Traditional HTTP request scheduling schemes can achieve this, but they schedule requests to manage only one server resource, such as CPU or disk I/O. Actually, processing a request on the server will consume multiple resources. This paper presents a multiple-resource request scheduling algorithm, called mQoS, for differentiating the utilization of the server resource. The mQoS scheduler consists of several sub-schedulers and a main scheduler. Each sub-scheduler manages a server resource to differentiate its utilization among the classes. The main scheduler checks the availability of every server resource and triggers an appropriate sub-scheduler to balance the utilization of server resources. The implementation of the mQoS gateway is based on Squid and Linux. The evaluation compares the mQoS scheduling with no scheduling (nQoS) and single-resource request scheduling (sQoS). The mQoS scheduling reveals the accurate differentiation on every server resource. In addition, the total server throughput in the mQoS scheduling is improved by 21%, compared with the sQoS scheduling. The average user-perceived latency of the mQoS scheduling is also shorter than other scheduling.