[ndnSIM] Cache sizes in different Cache Replacement Algorithms

[Alex Afanasyev]

Hi Abhijith,

The cache replacement policy by itself would not change how the cache behavior if there is a sequential request for unique data (as in the scenario that just demonstrates how to set up the trace).  You need to design the scenario where you have repetitive requests for the same data, e.g., using ConsumerZipfMandelbrot app.

---
Alex

> On May 5, 2016, at 4:45 AM, Abhijith Anilkumar <abhijithabhayam at gmail.com> wrote:
> 
> Hello everyone,
> 
> I had been trying to compare the different cache replacement algorithms for different cache sizes. I tried the CSTracer example given in the ndnSIM site. I'm trying to generate the CSTracer output for different cache replacement algorithms and cache sizes by modifying the line "ndnHelper.SetOldContentStore("ns3::ndn::cs::Lru", "MaxSize", "100");".
> 
> But, whatever changes I make to the cache size, the output from the CSTracer is the same. I'm a newbie to ndnSIM. What am I doing wrong here? Can anybody help me with this ?
> 
> Regards,
> Abhijith
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20160505/6423f81f/attachment.bin>