互联网Web缓存策略研究综述

需积分: 9 50 浏览量更新于2024-09-17 收藏 126KB PDF 举报

"A Survey of Web Caching Schemes for the Internet" 网络缓存是解决互联网上因数据量巨大而导致的网络拥塞和服务器过载问题的关键技术。随着万维网（World Wide Web）的指数级增长，用户访问延迟、服务器压力和网络流量增加成为显著问题。Web缓存通过在本地存储常用的数据对象副本，减少了对远程服务器的请求，从而改善了性能，降低了网络带宽需求。 Web缓存系统的核心元素包括： 1. **缓存代理服务器**：作为用户和原始服务器之间的中介，负责存储和提供缓存内容。 2. **缓存策略**：决定哪些内容应被缓存，以及何时更新或替换缓存中的内容。常见的缓存策略有LRU（最近最少使用）、LFU（最不经常使用）和FIFO（先进先出）等。 3. **缓存一致性协议**：确保多台缓存服务器间内容的一致性，如HTTP的强一致性（Strong Cache Validation）和弱一致性（Weak Cache Validation）。 4. **缓存替换策略**：当缓存空间有限时，选择哪种内容应该被替换出去。 5. **内容分发网络（CDN）**：通过在全球部署分布式节点，将内容更靠近用户，进一步提高访问速度和可用性。该论文综述了Web缓存领域的最新技术，包括但不限于： - **预测性缓存**：通过分析用户行为模式来预测未来可能请求的内容。 - **动态适应性缓存**：根据网络状况和用户需求动态调整缓存策略。 - **智能缓存**：利用机器学习算法优化缓存决策，提升命中率。 - **多级缓存**：在不同层次（如客户端、接入点、区域中心等）设置缓存，形成层次化的缓存结构。研究前沿主要集中在以下几个方向： 1. **缓存预取技术**：利用大数据分析和人工智能预测用户可能的需求，提前加载内容。 2. **自适应缓存策略**：自动调整以适应不断变化的网络环境和用户行为。 3. **边缘计算与缓存结合**：在边缘计算节点上实现缓存，减少数据中心的负载。 4. **区块链在缓存一致性中的应用**：利用区块链技术保证分布式缓存的数据一致性与安全性。 Web缓存的研究不仅提高了互联网的性能，也对云计算、物联网(IoT)和5G网络等新兴领域产生了深远影响。未来的挑战在于如何在保持高效缓存的同时，兼顾隐私保护、安全性和资源的有效利用。

clients

Web server Web server

proxy

cooperation

Figure 3: A generic WWW caching system.



Fast access. From users’ point of view, access latency is an

important measurement of the quality of Web service. A de-

sirable caching system should aim at reducing Web access

latency. In particular, it should provide user a lower latency

on average than those without employing a caching system.



Robustness. From users’ prospect, the robustness means

availability, which is another important measurement of qual-

ity of Web service. Users desire to haveWeb service available

whenever they want. The robustness has three aspects. First,

it’s desirable that a few proxies crash wouldn’t tear the en-

tire system down. The caching system should eliminate the

single point failure as much as possible. Second, the caching

system should fall back gracefully in case of failures. Third,

the caching system would be design in such a way that it’s

easy to recover from a failure.



Transparency. A Web caching system should be transparent

for the user, the only results user should notice are faster re-

sponse and higher availability.



Scalability. We have seen an explosive growth in network

size and density in last decades and is facing a more rapid

increasing growth in near future. The key to success in such

an environment is the scalability. We would like a caching

scheme to scale well along the increasing size and density of

network. This requires all protocols employed in the caching

system to be as lightweight as possible.



Efﬁciency. There are two aspects to efﬁciency. First, how

much overhead does the Web caching system impose on net-

work? We would like a caching system to impose a minimal

additional burden on the network. This includes both control

packets and extra data packets incurred by using a caching

system. Second, the caching system shouldn’t adopt any

scheme which leads to under-utilization of critical resources

in network.



Adaptivity. It’s desirable to make the caching system adapt

to the dynamic changing of the user demand and the network

environment. The adaptivity involves several aspects: cache

management, cache routing, proxy placement, etc. This is

essential to achieve optimal performance.



Stability. The schemesused in Web caching system shouldn’t

introduce instabilities into the network. For example, naive

cache routing based on dynamic network information will re-

sult in oscillation. Such an oscillation is not desirable since

the network is under-utilization and the variance of the access

latency to a proxy or server would be very high.



Load balancing. It’s desirable that the caching scheme dis-

tributes the load evenly through the entire network. A sin-

gle proxy/server shouldn’t be a bottleneck (or hot spot) and

thereby degrades the performance of a portion of the network

or even slow down the entire service system.



Ability to deal with heterogeneity. As networks grow in scale

and coverage, they span a range of hardware and software

architectures. The Web caching schemeneed adapt to a range

of network architectures.



Simplicity. Simplicity is alwaysan asset. Simpler schemesare

easier to implement and likely to be accepted as international

standards. We would like an ideal Web caching mechanism

to be simple to deploy.

4 Web caching schemes

Havingdescribedthe attributes of an ideal Web cachingsystem, we

now survey some schemes described in the literature and point out

their inadequacies.

4.1 Caching architectures

The performance of a Web cache system depends on the size of its

client community; the bigger is the user community, the higher is

the probability that a cached document (previously requested) will

soon be requested again. Caches sharing mutual trust may assist

each other to increase the hit rate. A caching architecture should

provide the paradigm for proxies to cooperate efﬁciently with each

other.

4.1.1 Hierarchical caching architecture

One approach to coordinate caches in the same system is to set up

a caching hierarchy. With hierarchical caching, caches are placed

at multiple levels of the network. For the sake of simplicity, we

assume that there are four levels of caches: bottom, institutional,

regional, and national levels [69]. At the bottom level of the hier-

archy there are the client/browser caches. When a request is not

satisﬁed by the client cache, the request is redirected to the institu-

tional cache. If the document is not found at the institutional level,

the request is then forwarded to the regional level cache which in

turn forwards unsatisﬁed requests to the national level cache. If the

document is not found at any cache level, the national level cache

contacts directly the original server. When the document is found,

either at a cache or at the original server, it travels down the hier-

archy, leaving a copy at each of the intermediate caches along its

path. Further requests for the same document travel up the caching

hierarchy until the document is hit at some cache level.

Hierarchical Web caching was ﬁrst proposed in the Harvest

project [14]. Other examples of hierarchical caching are Adaptive

Web caching [58], Access Driven cache [83], etc. A hierarchical

architecture is more bandwidth efﬁcient, particularly when some

cooperating cache servers do not have high-speed connectivity. In

such a structure, popular Web pages can be efﬁciently diffused to-

wards the demand. However, there are several problems associated

with a caching hierarchy [69] [71]:

剩余10页未读，继续阅读

zhaoym_ndsc

粉丝: 0
资源: 2

互联网Web缓存策略研究综述

严重 [RMI TCP Connection(3)-127.0.0.1] org.apache.catalina.core.StandardContext.startInternal Error-附件资源

A Survey of Caching Mechanisms in

A Framework of Cooperative Cell Caching for the Future Mobile Networks

Two Anonymous Cooperative Caching Schemes in Mobile Ad Hoc Networks

A Web Caching Primer

A web caching primer

web caching

Web Caching

A Hybrid Strategy for Caching Web Search Engine Results

最新资源