1
Progressive Caching in CCNAuthors: Jason Min Wang, Brahim BensaouPublisher: GLOBECOM 2012Presenter: Chai-Yi ChuDate: 2013/05/08
2
Introduction Proposed Caching Management Scheme◦Caching Decision Policy◦Replacement Strategies
Simulation◦ Experimental Methodology◦ Experiment Results
Outline
3
propose a new caching scheme for such CCN networks and evaluate the in-network caching performance of this policy by comparing it with that of the default proposed policy via simulation.
Introduction
4
Characteristics that have crucial influence on the caching performance
1. Locality of references2. Content popularity distribution3. One-time referencing4. Heavily-tailed object size distribution
5
Caching Decision Policy◦Resemblance to the LCD algorithm (Leave Copy Down)◦Choosing the immediate downstream node of the cache hit
point as the primary candidate place to replicate the data packet.
Proposed Caching Management Scheme
6
7
◦ : the number of interfaces saved in the PIT entry, that is, from how many distinct interfaces requests for the same namedchunk are aggregated.
◦ : the actual number of individual requests for p at an edge node.
8
9
Replacement Strategies◦ Edge nodes
A modification of the Greedy Dual-size algorithm. Each cached chunk of data is associated with a value . : the hop count needed to fetch the packet. An “inflation” value .
10
11
◦ Intermediate nodes Each cached chunk of data is associated with a value . Interface Diversity information will be recorded in and is used to leave
breadcrumbs on the access statistics of after it has been cached.
12
13
Implemented a simplified CCN model on top of Omnet++◦ simulation model includes three basic components of CCN
i.e., CS, PIT and FIB◦ other features of CCN (e.g., hierarchical naming, routing,
security issues and so on) are not taken into account.
Simulation
14
Experimental Methodology◦Network topology
15
◦Workloads The synthetic Web workload generator ProWGen is used to
generate workloads for the two content servers.
16
◦ Performance metric systematic hit gain : the distance between node and the original content server. : the amount of pending requests at edge nodes for the hitting
data. : the size of object (chunks). : the hop distance between node and the original content server
of object . The closer the value of G is to 1, the better the in-network
caching system performs.
17
◦Methodology cache size
varied uniformly from 100 to 8,000 chunks for all nodes. The chunk size is set 10KB
request aggregation request aggregation time can change the observed access pattern
and thus impact the hit rates of the nodes. cache management scheme
1. alwayscache+LRU (the initial proposal of CCN2. proposed PCP+heterogeneous replacement algorithms
18
Impacts of cache size and content popularity
Experiment Results
19
20
Impact of request aggregation