Final answer:
a) The average LAN utilization is 7.5% and the access link utilization is 5%. b) With the addition of a web cache, the access link utilization becomes 3%. c) The savings in average time to retrieve the whole web page between cases a) and c) is 50 msec. d) No calculation for parallel, persistent, and pipelined HTTP.
Step-by-step explanation:
a) To calculate the average LAN utilization, we need to find the rate at which packets are being sent over the LAN compared to its capacity. Since each object is 50 Kbits and can fit in a single packet, the size of each packet is 50 Kbits. The rate of the LAN is 10Mbps, which is equivalent to 10,000,000 bits per second. Therefore, the average LAN utilization is:
Average LAN utilization = (Rate at which packets are being sent over the LAN) / (Capacity of the LAN)
= (5 requests per second) * (3 objects) * (50 Kbits per object) / (10,000,000 bits per second)
= 0.075 or 7.5%
To calculate the access link utilization, we need to find the rate at which packets are being sent over the access link compared to its capacity. The rate of the access link is 1.5Mbps, which is equivalent to 1,500,000 bits per second. Therefore, the access link utilization is:
Access link utilization = (Rate at which packets are being sent over the access link) / (Capacity of the access link)
= (5 requests per second) * (3 objects) * (50 Kbits per object) / (1,500,000 bits per second)
= 0.05 or 5%
b) With the addition of a web cache that can send the local copy of the web page for 40% of the requests, the average LAN utilization remains the same as before, as the LAN is still being utilized for all requests. However, the access link utilization decreases, as 40% of the requests no longer need to go through the access link. Therefore, the new access link utilization is:
New access link utilization = (Rate at which packets are being sent over the access link) / (Capacity of the access link)
= (5 requests per second) * (3 objects) * (50 Kbits per object) * (0.6) / (1,500,000 bits per second)
= 0.03 or 3%
c) To calculate the savings in the average time to retrieve the whole web page between case a) and case c) for non-persistent, non-parallel, non-pipelined HTTP, we need to consider the number of round trips between the users and the web server. In case a), each object requires a round trip, so the total number of round trips is 3. In case c), with the web cache sending the local copy for 40% of the requests, 2 objects require a round trip and 1 object can be retrieved from the cache with no round trip required. Therefore, the average time to retrieve the whole web page in case a) is:
Average time in case a) = (Number of objects) * (RTT between two end systems)
= 3 * 50 msec
And the average time to retrieve the whole web page in case c) is:
Average time in case c) = (Number of round trips for objects requiring round trips) * (RTT between two end systems)
= 2 * 50 msec
The savings in the average time to retrieve the whole web page between case a) and case c) is the difference between the average time in case a) and case c):
Savings = (Average time in case a) - (Average time in case c))
= (3 * 50 msec) - (2 * 50 msec)
= 50 msec
d) To calculate the savings in the average time to retrieve the whole web page for parallel, persistent, and pipelined HTTP, we need to consider the number of parallel connections and the number of objects requested in parallel. In the case of parallel, persistent, and pipelined HTTP, multiple requests can be sent over a single TCP connection and multiple responses can be received in parallel. However, in this scenario, we do not have enough information to calculate this value.