[Nfd-dev] RTT delay caused by RIB registration commands

Junxiao Shi shijunxiao at email.arizona.edu
Fri Apr 24 11:38:41 PDT 2015

Hi Lan

Before I can suggest any code patches, additional experiment is needed to
confirm or reject the hypothesis in
http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2015-April/001049.html .

If you want to measure RTT changes due to route changes, one possible way
is to increase the link delay.
When the link delay is 10ms, a 10ms RTT change is 50% and appears
When the link delay is 500ms, a 10ms RTT change is 1% and appears

Yours, Junxiao

On Fri, Apr 24, 2015 at 11:33 AM, Lan Wang (lanwang) <lanwang at memphis.edu>

>  Basically, we saw a large jump in ndnping results between two nodes even
> though there was no path change for the path between those two nodes.  We
> found that it was because those nodes (or the intermediate ones) were busy
> updating their FIB (for other routes) -- each registration and
> unregistration of a route obviously took ~10ms for NRD/NFD to process.
>  We were interested in RTT changes due to route changes, so the extra
> delay caused by the route registrations is an undesirable side effect we'd
> like to remove (thus Vince's email).  So any suggestions on how to deal
> with this in our experiments are highly appreciated.
>  In the long term, we do need to address the problem of high processing
> delays of route registrations.
> Lan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150424/b116f66b/attachment.html>

More information about the Nfd-dev mailing list