[ndnSIM] Installing cache policy in specific nodes and cache hit rates

Spyridon Mastorakis smastorakis at unomaha.edu
Sun Jan 5 09:14:07 PST 2020

Please see inline.

On Jan 2, 2020, at 2:51 PM, Samar Alduayji via ndnSIM <ndnsim at lists.cs.ucla.edu<mailto:ndnsim at lists.cs.ucla.edu>> wrote:

Dear All,

I'm using the StackHelper to implement the caching policy with the function SetOldContentStore to use the freshness policy and I have several questions:

1- Does the freshness policy still working? I use the "ns3::ndn::cs::Freshness::Lru" and I have two producers each has different freshness values. I edited the consumer class to enforce asking for fresh data only ( using the MustBeFresh flag). Do I need to change any other classes?

Yes, it should still be working.

2- I'm trying to implement the caching policy in some nodes only and I tried to use stackHelper.Install( Ptr<Node> node) instead of InsallAll(), but it didn't work and I got the following message ( terminated with signal SIGSEGV).

Something is seg faulting, use your debugger to figure out.

3- Maybe a dummy question. For the cached data in the content store, how the freshness value decreases over time?

Not sure I understand the question.

4- I'm using CsTracer to get the cache hits and misses, and I'm trying with different caching polices ( old content store ones), different consumers frequency rates and different freshness values. However, the results are almost the same for all trails with high cache misses and low cache hits. How can I get better results?

This heavily depends on the simulation setup and objectives.


Spyridon (Spyros) Mastorakis
Assistant Professor
Computer Science Department
University of Nebraska, Omaha
Peter Kiewit Institute Room 175A
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20200105/d967ec03/attachment.html>

More information about the ndnSIM mailing list