[Ndn-interest] Multi-path retrieval performance

[Nick Briggs]

One other thing -- if the links are over TCP you probably want to know the net.inet.tcp.sendspace and .recvspace settings (or equivalent, and possibly other network configuration parameters).   If you end up with a producer process being suspended/rescheduled because it has overrun the TCP output buffer space it can introduce hiccups into the performance...

-- Nick

> On Sep 18, 2017, at 2:22 PM, Klaus Schneider <klaus at cs.arizona.edu> wrote:
> 
> + What's the exact simulation setup? Topology, link bandwidth, delays, etc. ?
> 
> On 09/17/2017 03:08 PM, Mohammad Alhowaidi wrote:
>> Hello,
>> I was trying to do a load balancing (multi-path retrieval) experiments to get a fast retrieval for a file.
>> for example I have a router connected to three producers. and I used ndncatchunk to retrieve a file (1GB) and I started to increase the interest pipeline value.
>> I found that when the value of interest-pipeline is 10 is the best when retrieving from one producer (not sure *WHY*? ), then I tried to use 2 producers with interest-pipeline is 20 and get a better performance (retrieving chunks was divided evenly between these two producers).
>> But when I used 3 producers the performance reduced, whatever I choose the interest-pipeline value. Shouldn't retrieving the file from 3 producers with 30 interest-pipeline value be better? what could be the problem?
>> Sorry for the long question!
>> Thanks,
>> Mohammad
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest