[Mini-NDN] Logging module for PIT and FIB

[Aman Maldar]

Good to know. Very relevant discussion to my questions. Well, I will work
things out by adding some log statements.

On the same note, how do I measure PIT lookup time?

Let's say, in pit-entry.cpp following code change makes sense? Or am I
looking at the wrong file/wrong logic itself?


bool
Entry::canMatch(const Interest& interest, size_t nEqualNameComps) const
{
BOOST_ASSERT(m_interest->getName().compare(0, nEqualNameComps,
interest.getName(), 0, nEqualNameComps) == 0);
   //declare boolean = result // capture time t1
result = m_interest->getName().compare(nEqualNameComps, Name::npos,
interest.getName(), nEqualNameComps) == 0 &&
m_interest->getSelectors() == interest.getSelectors();
// capture time t2 // calculate diff (this is PIT lookup time) // return
result; /// \todo #3162 match Link field
}

Thanks.

On Mon, Nov 27, 2017 at 6:03 PM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> nfd-status can give you the number of entries, something like:
>
>            nFibEntries=4
>            nPitEntries=7
>
> But there is no other logging for PIT or FIB.
> Some discussion here:
> http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2016-August/001969.html
>
> Ashlesh
>
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Aman
> Maldar <amanmaldar at gmail.com>
> *Sent:* Monday, November 27, 2017 4:55:20 PM
> *To:* mini-ndn at lists.cs.ucla.edu
> *Subject:* [Mini-NDN] Logging module for PIT and FIB
>
> I read pretty interesting discussion on NFD mail archive regarding
> measuring/improving performance for PIT and FIB.
>
> I am trying to test performance of PIT, FIB in terms of time response for
> variety of interests and large number of entries in PIT and FIB.
> I decided to print hit/miss scenario log for both. I just want to double
> check if NFD already have logging module available for this?
>
> Are below 2 files that I can add my logs to, to see them in execution?
> Correct me.These 2 files doesn't have any logging module added.
>
> https://github.com/named-data/NFD/blob/master/daemon/table/pit-entry.cpp
>
> https://github.com/named-data/NFD/blob/master/daemon/table/fib-entry.cpp
>
>
> Which nfd modules should be used to during tracing?
>
> Available logging modules:
> AccessStrategy, AsfMeasurements, AsfStrategy, AutoPrefixPropagator,
> BestRouteStrategy2, ClientControlStrategy, CommandAuthenticator,
> ContentStore, CsPolicy, DeadNonceList, EthernetFactory,
> EthernetTransport,FaceManager , FaceSystem .FaceTable ,FibManager
> ,FibUpdater Forwarder, GeneralConfigSection, GenericLinkService,
> InternalClientTransport, InternalForwarderTransport, LinkService
> LoggerFactory LpFragmenter LpReassembler MulticastEthernetTransport
> MulticastStrategy MulticastUdpTransport NFD NameTree NameTreeHashtable
> NameTreeIterator  NetworkInterfaceInfo Nfd
> NfdRibReadvertiseDestination PrivilegeHelper ProcessNackTraits
> Readvertise ReadvertiseDestination Rib RibEntry RibManager  Strategy
> StrategyChoice StrategyChoiceManager TcpChannel
> TcpFactory TcpTransport Transport UdpChannel UdpFactory
> UnicastEthernetTransport UnicastUdpTransport UnixStreamChannel
> UnixStreamFactory UnixStreamTransport
>
> Thanks in advance.
>
> --
> *Regards,*
> * Mr. Maldar Aman M.*
> *University of Massachusetts, Lowell*
>



-- 
*Regards,*
*Mr. Maldar Aman M.*
*University of Massachusetts, Lowell*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20171127/b0c15a6f/attachment-0001.html>