[Ndn-interest] Configuration of Content Store
aa at CS.UCLA.EDU
Tue Sep 8 23:31:00 PDT 2015
I want to clarify a potential confusion thing. Any arriving data packet is opportunistically cached and evicted only when there is no more space for newly received data.
The effect you're observing is because in your evaluations you're using "MustBeFresh" selector (in some libraries, it is currently on by default and you need to explicitly turn it off). The primary use case for this selector is to allow name discovery (get "fresher" data for some prefix), and this freshness period is determined by what has been specified in the received data packet.
When you send interests with MustBeFresh selector, they can only match to CS entries that contain "fresh" data. I think this is why you're observing your ~10 second "cache lifetime".
It is "ndn-cxx" :)
> On Sep 8, 2015, at 1:26 AM, Matti Lorenzen <matti.lorenzen at tum.de> wrote:
> During the last days I have evaluated transmission times between NDN nodes and noticed that the files are only cached in the Content Store for a very short amount of time (10 seconds approx.). I ran this with ccn-cxx 0.3.4 and the corresponding NFD.
> Is this normal? In nfd.conf, the default size for the CS is 65536 packets, so I was surprised by such a short lifetime.
> I saw that you recently discussed about CS configuration (http://redmine.named-data.net/issues/3148) and am wondering whether the lifetime can already be changed at the current version. If not, where in the cxx-code is it defined so I can make alterations?
> Best regards and thank you in advance,
> also sorry for bothering everybody again,
> Matti Lorenzen
> Matti Lorenzen
> IAESTE LC München - Outgoing
> IAESTE Central European Region - Trainings Coordinator
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Ndn-interest