36
Client Cache Management Improving the broadcast for one probability access distribution will hurt the performance of other clients with different access distributions. Therefore the client machines need to cache pages obtained from the broadcast.

Client Cache Management

  • Upload
    nayef

  • View
    33

  • Download
    0

Embed Size (px)

DESCRIPTION

Client Cache Management. Improving the broadcast for one probability access distribution will hurt the performance of other clients with different access distributions. Therefore the client machines need to cache pages obtained from the broadcast. Client Cache Management. - PowerPoint PPT Presentation

Citation preview

Page 1: Client Cache Management

Client Cache Management Improving the broadcast for one

probability access distribution will hurt the performance of other clients with different access distributions.

Therefore the client machines need to cache pages obtained from the broadcast.

Page 2: Client Cache Management

Client Cache Management With traditional caching clients cache

the data most likely to be accessed in the future.

With Broadcast Disks, traditional caching may lead to poor performance if the server’s broadcast is poorly matched to the clients access distribution.

Page 3: Client Cache Management

Client Cache Management In the Broadcast Disk system, clients

cache the pages for which the local probability of access is higher than the frequency of broadcast.

This leads to the need for cost-based page replacement.

Page 4: Client Cache Management

Client Cache Management One cost-based page replacement strategy

replaces the page that has the lowest ratio between its probability of access (P) and its frequency of broadcast (X) - PIX

PIX requires the following:

1 Perfect knowledge of access probabilities.

2 Comparison of PIX values for all cache resident pages at cache replacement time.

Page 5: Client Cache Management

Example One page is accessed 1% of the

time at a particular time and is also broadcast 1% of the time.

Second page is accessed only 0.5% but is broadcast 0.1% of time

Which page to be replaced

Page 6: Client Cache Management

Client Cache Management Another page replacement strategy adds

the frequency of broadcast to an LRU style policy. This policy is known as LIX.

LIX maintains a separate list of cache-resident pages for each logical disk

A page enters the chain corresponding to the disk in which it is broadcast

Each list is ordered based on an approximation of the access probability (L) for each page.

Page 7: Client Cache Management

Cont.

When a page is hit, it is moved to top of chain and when a new page is entered >

A LIX value is computed by dividing L by X, the frequency of broadcast for the page at the bottom of each chain

The page with the lowest LIX value is replaced.

Page 8: Client Cache Management

Prefetching An alternative approach to obtaining

pages from the broadcast. Goal is to improve the response time of

clients that access data from the broadcast.

Methods of Prefetching:

Tag Team Caching

Prefetching Heuristic

Page 9: Client Cache Management

Prefetching Tag Team Caching - Pages continually

replace each other in the cache. For example two pages x and y, being

broadcast, the client caches x as it arrives on the broadcast. Client drops x and caches y when y arrives on the broadcast.

Page 10: Client Cache Management

10

Prefetching Simple Prefetching Heuristic Performs a calculation for each page that

arrives on the broadcast based on the probability of access for the page (P) and the amount of time that will elapse before the page will come around again (T).

If the PT value of the page being broadcast is higher than the page in cache with the lowest PT value, then the page in cache is replaced.

Page 11: Client Cache Management
Page 12: Client Cache Management
Page 13: Client Cache Management
Page 14: Client Cache Management
Page 15: Client Cache Management
Page 16: Client Cache Management
Page 17: Client Cache Management
Page 18: Client Cache Management
Page 19: Client Cache Management
Page 20: Client Cache Management
Page 21: Client Cache Management
Page 22: Client Cache Management
Page 23: Client Cache Management
Page 24: Client Cache Management
Page 25: Client Cache Management
Page 26: Client Cache Management
Page 27: Client Cache Management
Page 28: Client Cache Management
Page 29: Client Cache Management
Page 30: Client Cache Management
Page 31: Client Cache Management
Page 32: Client Cache Management
Page 33: Client Cache Management
Page 34: Client Cache Management
Page 35: Client Cache Management
Page 36: Client Cache Management