8.6 Adding More Servers

The original online auction site assumes that there is a single Web server, a single application server, and a single database server. In general, there may be many identical servers in each tier. Consider a simple case of Nws identical Web servers and a perfect load balancer that sends exactly 1/Nws of the traffic to each Web server. Thus, the average arrival rate of requests at each Web server is equal to l/Nws, where l is the overall arrival rate of requests to the site. In the following analysis, the application and database servers are ignored. Also, consider a single class of requests. The generalization to multiple classes is straightforward.

One way of modeling the Nws-server situation is to replicate all queues that represent the devices (e.g., CPU, disks) of a Web server in the QN model so that there are Nws of each device in the QN model. Given the assumption of identical Web servers and perfect load balancing, a simpler approach can be followed where all Nws Web servers are represented in the QN model by a single equivalent Web server. The model is constructed so that the average response time of the set of Nws servers is the same as that of the single equivalent server. Figure 8.5 illustrates this situation.

Figure 8.5. Single Web server equivalent to multiple Web servers.


The response time of a request that goes through server j(j = 1, ···, Nws) of Fig. 8.5(a) is the same as the response time of the single equivalent Web server of Fig. 8.5(b) with an arrival rate equal to l/Nws. (The two models have the same service demands at the CPU and disk devices.) The response time at the single equivalent server of Fig. 8.5(b) is given by

Equation 8.6.17


where K is the number of devices (i.e., CPU ands disk) and Di (i = 1, ···, K) is the service demand of a request at device i. Note that the term (l/Nws) Di is the utilization of device i according to the Service Demand Law. The generalization of Eq. (8.6.17) to multiple classes is

Equation 8.6.18


where Rr is the average response time of class r requests, lr is the average arrival rate of requests of class r, and graphics/215fig01.gif Di,r is the total utilization of device i over all R classes.

As an example, consider the service demands of Table 8.4 and an overall session start rate g of 11 sessions/sec. Then, consistent with the example in Section 8.3, assume 25% of type A customers and 75% of type customers. Then, the arrival rates for each type of request are given by lhome = 11.0 requests/sec, lsearch = 13.71 requests/sec, lview = 2.22 requests/sec, llogin = 3.68 requests/sec, lcreate = 1.10 requests/sec, and lbid = 2.10 requests/sec.

Consider three Web servers instead of one. The utilizations of the CPU and disk at the single equivalent Web server are given by




Then, the response times of each of the six classes of requests at the Web server tier are computed using Eq. (8.6.18) as


The same approach of replacing all servers of the Web tier by a single equivalent Web server can be applied to the application and database tiers.

Performance by Design. Computer Capacity Planning by Example
Performance by Design: Computer Capacity Planning By Example
ISBN: 0130906735
EAN: 2147483647
Year: 2003
Pages: 166

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net