[Nfd-dev] Memory related issues with NFD.

Anil Jangam anilj.mailing at gmail.com
Wed May 4 13:47:53 PDT 2016


Here are some more data points from Valgrind Massiff analysis. I have ran
it for 25 and 50 nodes.

/anil.


On Wed, May 4, 2016 at 2:26 AM, Anil Jangam <anilj.mailing at gmail.com> wrote:

> Hi Junxiao,
>
> The memory leak is now closed by back porting the fix you referred to.
> However, the growth in memory consumption is still evident. This time, I
> believe it is a bloating of the process size. Can you please comment
> looking at the attached Valgrind logs if this is a legitimate requirement
> of NFD or it is just holding up the resources without really needing it?  I
> see the allocation emanating from RibManager and on receiving Interest as
> some of the major contributors.
>
> Likewise you said earlier, these are perhaps fixed into main branch of NFD
> but not ported yet into the NFD of ndnSIM. Please check, reports are
> attached.
>
> 50 node simulation valgrind summary:
> -------------------------------------------------------
> ==9587== LEAK SUMMARY:
> ==9587==    definitely lost: 0 bytes in 0 blocks
> ==9587==    indirectly lost: 0 bytes in 0 blocks
> ==9587==      possibly lost: 2,263,514 bytes in 67,928 blocks
> ==9587==    still reachable: 1,474,943,776 bytes in 3,910,237 blocks
> ==9587==         suppressed: 0 bytes in 0 blocks
> ==9587==
> ==9587== For counts of detected and suppressed errors, rerun with: -v
> ==9587== ERROR SUMMARY: 37 errors from 37 contexts (suppressed: 0 from 0)
>
> 25 node simulation valgrind summary:
> -------------------------------------------------------
> ==9287== LEAK SUMMARY:
> ==9287==    definitely lost: 0 bytes in 0 blocks
> ==9287==    indirectly lost: 0 bytes in 0 blocks
> ==9287==      possibly lost: 400,259 bytes in 11,100 blocks
> ==9287==    still reachable: 437,147,930 bytes in 1,132,024 blocks
> ==9287==         suppressed: 0 bytes in 0 blocks
> ==9287==
> ==9287== For counts of detected and suppressed errors, rerun with: -v
> ==9287== ERROR SUMMARY: 31 errors from 31 contexts (suppressed: 0 from 0)
>
> /anil.
>
>
>
>
> On Tue, May 3, 2016 at 7:42 AM, Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
>
>> Hi Anil
>>
>> The call stack in the Valgrind report indicates that you are running NFD
>> within ndnSIM.
>> #3236 is fixed in NFD commit 9c903e063ea8bdb324a421458eed4f51990ccd2c on
>> Oct 04, 2015. However, ndnSIM's NFD fork is dated back on Aug 21, 2015, and
>> doesn't contain the fix.
>> You may try to backport that commit to ndnSIM's NFD fork, or ask ndnSIM
>> developers to upgrade their fork.
>>
>> Yours, Junxiao
>>
>>
>> On Mon, May 2, 2016 at 5:23 PM, Anil Jangam <anilj.mailing at gmail.com>
>> wrote:
>>
>>> Hi Junxiao,
>>>
>>> I am observing a memory leak with NFD and to verify the same I did
>>> couple of Valgrind enabled simulation runs with 25 and 50 nodes. Based on
>>> the Valgrind report, and output of 'top' command, I see that RAM
>>> consumption grows consistently and rapidly. My scaling test is affected
>>> that I am not able to run the simulation for longer time and/or with high
>>> number of nodes. Also, I see a very high number of timeouts
>>>
>>> I see a NFD leak issue in closed state, which confirms this leak however
>>> closed owing to its small size. Perhaps this is showing up a high scale?
>>> http://redmine.named-data.net/issues/3236/
>>>
>>> Please check the attached Valgrind report. Let me know what other data
>>> you may need to debug this further. Also, please suggest a solution or
>>> workaround to this?
>>>
>>> /anil.
>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160504/bec6292c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 25_nodes_massiff_data.png
Type: image/png
Size: 217309 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160504/bec6292c/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 50_nodes_massiff_data.png
Type: image/png
Size: 158493 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160504/bec6292c/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 25_50_nodes_massiff.tar.gz
Type: application/x-gzip
Size: 306048 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160504/bec6292c/attachment.bin>


More information about the Nfd-dev mailing list