[Mini-NDN] NdnRoutingHelper error in large topologies

[Philipp Moll]

Hi Saurab,


thanks for looking in to that issue. The routing helper was my first 
choice because I thought it would minimize unforeseen side effects 
resulting from routing protocols in my evaluation. Do you think that 
using NLSR would be the better (faster / more stable / more resilient) 
choice for doing evaluations using MiniNDN?


My observation yesterday indicated that the lag results from 
registerRoute, not createFace in nfdc.py. This is why I achieved a 
significant speedup with my hack to only register one route only. But it 
seems that//I don't need //my hack anymore. Thanks for fixing the issue.


Best
Philipp


On 3/2/20 11:23 PM, Saurab Dulal (sdulal) wrote:
> Hi Philipp,
>
> Thank you so much for reporting the problem. I have found the bug and 
> also have uploaded a patch in the gerrit. 
> https://gerrit.named-data.net/c/mini-ndn/+/5957
>
> However, your topology (45 nodes, 71 links) should be easily handled 
> by minindn without routing helper (unless you specifically need it). I 
> ran your topology with minindn in a vagrant box (4 gigs ram) without 
> routing helper and it converged successfully in less than 5 minutes. I 
> have also tested larger size topologies i.e. 150+ nodes, and 700+ 
> links and they all have converged successfully.
>
> I did some benchmark testing and found out that routing-helper 
> especially in case of all face, link-state is pretty slow. But this is 
> normal because you are creating an enormous amount of routes. With a 
> single face, it's much better. Most of the lags are caused by face 
> creation route addition. This is somewhat configurable in nfdc.py but 
> still, I was not able to improve performance significantly. I have 
> some improvements in my mind, just haven't got enough time to work on it.
>
> Regards,
> Saurab Dulal
>
>
>
>
>
> ------------------------------------------------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of 
> Philipp Moll <philipp.moll at itec.aau.at>
> *Sent:* Friday, February 28, 2020 3:29 PM
> *To:* mini-ndn at lists.cs.ucla.edu <mini-ndn at lists.cs.ucla.edu>
> *Subject:* [Mini-NDN] NdnRoutingHelper error in large topologies
> Hi guys,
>
> I am currently working on a MiniNDN scenario evaluation, where I need a
> large network topology. I pushed the Geant topology to gerrit yesterday.
> This topology has 45 nodes and quite high connectivity between the
> nodes. Installing all possible routes with the NdnRoutingHelper takes
> about 20 minutes. For me, this is too long when considering that my
> actual evaluation only takes 10 minutes.
>
> When restricting the routes to install to the shortest path only to save
> time (NdnRoutingHelper.calculateNPossibleRoutes(nFaces=1)), the
> computeDijkastra method fails in line 241 when using the Geant topology.
>
> I am not familiar with the ndn_routing_helper code, that's why I'll use
> a workaround. But maybe someone who is familiar with the routing-helper
> can find the problem's cause.
>
> Thanks,
> Philipp
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20200303/84d22d62/attachment.html>