[Mini-NDN] mini ndn performance

[Ashlesh Gawande (agawande)]

Scalability depends on the amount of CPU you have since we are running multiple instances of NFD and NLSR plus any other traffic.

It also depends on how much logging you have turned on and how much other things you are logging simultaneously.

If you are logging a lot of things I would suggest switching to RAM disk
(http://www.jamescoyle.net/how-to/943-create-a-ram-disk-in-linux)

And change all the instances of /tmp in mini-ndn to /mnt/ramdisk (if that is the name you have chosen for your ram disk).

If logging is not high then you will have to switch to a machine which has more CPU/cores.

Ashlesh
________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Navdeep Uniyal <navdeep.uniyal at neclab.eu>
Sent: Thursday, August 27, 2015 8:42 AM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] mini ndn performance


Hello all,



I am trying to run a 10 node network on a VM with following configuration:

[:/chipset_16px.png]


System


Base Memory:


5124 MB


Processor(s):


2


Execution Cap:


100%


VT-x/AMD-V:


Enabled


Nested Paging:


Enabled




Base System has Intel® Core2 Duo CPU @3.00 GHz.



With this configuration I am facing some performance issues while running nfd commands or while sending out interest messages. Could you please let me know if there is some minimum requirement to run minindn and what is the recommended configuration of the system.

With less node network it is working fine.







Best Regards,

Navdeep Uniyal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20150827/cae7cc77/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 174 bytes
Desc: image001.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20150827/cae7cc77/attachment.png>