[Nfd-dev] [EXT] NFD Profiling tool

[Davide Pesavento]

Ahmed,

I was referring specifically to those obsolete benchmark results on
redmine. Those tests were run over UDP, not Ethernet.

As for Ethernet faces, their implementation is substantially different
from UDP faces (libpcap vs sockets), and I really cannot say what the
bottleneck is, I've never profiled that part of NFD. Please let us
know if you find any issues in the code!

Regards,
Davide

On Fri, Dec 24, 2021 at 8:15 PM Ahmed Taffal <a.taffal96 at gmail.com> wrote:
>
> Thank you! it worked now.
>
> Regarding NFD performance, you said it depends on the CPU, but in my experiment when I used the NDNchunk tool to fetch a 100MB file (packet size to 8KB), I got a goodput of 43Mbps (it is calculated using the ndncatchunk), and the CPU usage of the NFD was not more than 15%. So, in this case, can I say that the reason for having this goodput is related to the NFD implementation? or there is a way to get better performance?
>
> Thanks in advance,
> Regards,
> Ahmed
>
> On Fri, 24 Dec 2021 at 20:36, Davide Pesavento <davidepesa at gmail.com> wrote:
>>
>> On Fri, Dec 24, 2021 at 7:48 AM Ahmed Taffal via Nfd-dev
>> <nfd-dev at lists.cs.ucla.edu> wrote:
>> >
>> > So I tried to use the gprof and I rebuilt the ndn-cxx and the NFD using this command CXXFLAGS="-o2 -g -pg -pedantic -Wall" ./waf configure. After terminating the NFD with nfd-stop I am not getting the gmon.out file. Should I use another method to terminate the NFD in order to get that file?
>>
>> Make sure you add "-pg" to the LINKFLAGS as well. Also please note
>> that the optimization flag is "-O2" with a capital "O".
>>
>> Davide