[Mini-NDN] result of a topology

Sun Nov 20 06:04:39 PST 2016

the delay is zero
the topology file is:
[nodes]
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6

On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> No, the figure of the paper should be possible to achieve. The CPU is the
> bottleneck because one has to run 6 NFD, 6 NLSR instances on a single
> machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB
> RAM and 2 CPUs without so much variation.
>
>
> To turn off the logs:
>
> Change DEBUG to NONE here:
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123
>
>
> and make sure that this also set to NONE:
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34
>
>
> Then reinstall Mini-NDN, sudo ./install.sh -i
>
>
> Also make sure that in your topology file all the log levels are set to
> NONE if there is such an option after the nodes.
>
>
> Then try to run the experiment again (If possible turn off the GUI in VM,
> i.e. login in to command line and run the experiment from there - just to
> free up some more CPU).
>
>
> In your graph the y-axis is the RTT in ms? What are the delays you have
> set on the links of the topology?
>
> (If possible, can you share the topology file?)
>
>
> Ashlesh
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Saturday, November 19, 2016 12:48:23 AM
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] result of a topology
>
> Hello,
> no there aren't any timeouts and what you see there is not a zero it is
> 10^0 which is equal to 1.
> I'm running my linux on a vmware virtual machine with the configurations
> bellow:
> [image: Inline image 1]
> so you're saying that this results which I've got in my figure is
> reasonable for the topology and it shouldn't exactly be like the figure in
> the paper?
> Thank you
>
> On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> Have you verified that the ping data is correctly depicted on your figure?
>>
>> Are there any timeouts in there? Because I see some zeros.
>>
>>
>> RTT can be have variation in Mini-NDN because of multiple NFDs are
>> running on the same machine.
>>
>> What is your current machine configuration?
>>
>> Usually for such a small topology it should not be a problem.
>>
>>
>> One thing you can try is that if you are collecting NFD, NLSR, or any
>> other logs, turn them off.
>>
>> That is turn off all the logs except the ping data.
>>
>>
>> Other thing to try is to use a machine with more CPU power.
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>> sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Friday, November 18, 2016 6:48:35 AM
>> *To:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* [Mini-NDN] result of a topology
>>
>> Hello all,
>> I'm new to mini-ndn and I'm trying to implement the following topology:
>> [image: Inline image 1]
>> so I use minindnedit to implement it with the following information:
>> [image: Inline image 2]
>> and based on the paper which represents this topology it is expected to
>> get this figure from it's information:
>> [image: Inline image 3]
>> which the blue "+" represents the ping-data in the case that no node
>> fails, but when I try to implement it using pingall experiment my figure
>> will come out like this:
>> [image: Inline image 4]
>> as you can see there is more swing in the blue '+'s than it is expected,
>> any idea why it is happening?
>> thank you
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>

-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0009.png>