NFD

Wonder what is the result format for this task?
When the test is done with gprof (callgrind/kcachegrind or whatever the tool is) on ONL, should I produce a report for it?

The outcome should a report on what areas of NFD is the current bottleneck.

Examples:

• PIT match algorithm for Interests with PublisherPublicKeyLocator consumes 40% of Interest processing time
• Memory allocation for Data packets takes 20% of total CPU time

Besides that, I assume that the target nfd is the latest one, not v0.1.0, correct?

ONL has nfd v0.1.0 installed, and I don't have privilege to install any library. My plan is install latest one in my home directory, and do performance profiling on it.

I think so.

According to the output, the nfd functions in the caller list (indirect caller) are nfd::AppFace::sign, ndn::keyChain::sign and ndn::keyChain::signPakcetWrapper, and ndn::SecTpmFile::signInTpm. nfd::ManagerBase::sendResponse, nfd::FaceManager::onRemoveFace, and nfd::ManagerBase::sendResponse etc. I believe they are from the channel setup process.

All those data are from the NDN router that connect to other routers, not from the ones directly connect to application. Let me analyze those data as well.

I checked the callgrind output from the nfd on a server and a client. No obvious bottlenecks found.

crypto functions are not the bottlenecks on nfd nodes which directly connect to clients/servers. Because they just need to setup the channel to the nfd routers.
There are lots of call to ndn::name class, which is reasonable, because clients keep sending Interest and fetch data.

nfd::NameTree::eraseEntryIfEmpty and nfd::Cs::find on the client node are relatively slow. They have small called number (around 14,000), and they take around 0.5% and 0.3% running time separately (In contrast, functions like ndn::name::at takes about 2.66% running time, and called number is above 7millions). But since they are not called frequently, they are not bottlenecks.

The above result is true for nfd::Cs::insertToSkipList and nfd::Cs::find on the server node. They have small called number(around 20,000). And the running time for both is around 0.2%.

What was the amount of forwarded Interests and Data packets?

Oh, I deleted that log by accident. Let me restate it using another output data:

1. According to the output on one server, 11685 Interests received (recorded by the traffic server). And nfd::Cs::insertToSkipList and nfd::Cs::find are called 11702 and 11701 separately, which is a little bit more than the Interests received by traffic server, probably comes from the channel setup process.

2. Similar to the output on one client. Total Interests Sent = 9019, Total Responses Received = 1717 (recorded by the traffic client). And nfd::NameTree::eraseEntryIfEmpty and nfd::Cs::find are called 9058, and 9061 separately.