[Ndn-interest] Regarding RTT for ndncatchunks in raspberry pi

[Athreya Nagaraj]

Hi all

I have used the term 'bus topology', which is wrong. The topology I have
used is 4 raspberry pi devices connected via 3 point-to-point links in a
linear fashion. I've attached a representative topology diagram. I
apologize for my mistake.

Thanks and Regards
Athreya H N

On Sun, Dec 29, 2019 at 10:39 PM Athreya Nagaraj <indiathreya92 at gmail.com>
wrote:

> Hi all
>
> I'm a student working on a testbed of NDN. The testbed consists of four
> raspberry pi connected in a bus topology. The two end devices act as
> producers and consumers for NDN data. The middle two devices act as
> routers. I use ndncatchunks to send a 100 MB file through the testbed. I
> observe that the RTT for this is significantly more (around 10 times more)
> than that for an FTP application on the same testbed. The throughput is
> also lesser compared to FTP (around 20% lesser for NDN). I was wondering
> what could cause this difference.
>
> Also, another observation I made was that when I was testing the testbed
> setup with ndnping, the RTT was not so high.
>
> I have also previously worked on similar topology with NDN and the
> machines used were desktop machines. In this case, NDN was better than FTP.
>
> Any thoughts on what could be causing this?
>
> Thanks and Regards
> Athreya H N
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20191230/e44014e2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled Diagram.png
Type: image/png
Size: 10243 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20191230/e44014e2/attachment.png>