From nou.mail at gmail.com Sun Jan 22 23:46:23 2017 From: nou.mail at gmail.com (Nour El Houda Ben Youssef) Date: Mon, 23 Jan 2017 08:46:23 +0100 Subject: [Mini-NDN] metric collection Message-ID: Dear community I am having troule to collect metrics after runing mini-ndn experiments I noticed tho following work: http://2nd-ndn-hackathon.named-data.net/mini-ndn-metrics/ It seems interesting, unfortunately there is no documentation on how building and using it can anybody help? best regards -- Nour El Houda Ben Youssef Koub?a PhD student Mobidoc - WEVIOO/SAGE/ENSI Master degree New Generation of Information Systems - FST Software Engineer - INSAT -------------- next part -------------- An HTML attachment was scrubbed... URL: From agawande at memphis.edu Mon Jan 23 15:15:45 2017 From: agawande at memphis.edu (Ashlesh Gawande (agawande)) Date: Mon, 23 Jan 2017 23:15:45 +0000 Subject: [Mini-NDN] metric collection In-Reply-To: References: Message-ID: What specific metrics are you having trouble collecting? That was a part of a hackathon effort of 1-2 days and hence lacks any documentation. The lead of that hackathon project has left our group so I do not have any information on it. Best would be to just go through the code that was added using git and try to figure it out. Ashlesh ________________________________ From: Mini-NDN on behalf of Nour El Houda Ben Youssef Sent: Monday, January 23, 2017 1:46 AM To: mini-ndn at lists.cs.ucla.edu Subject: [Mini-NDN] metric collection Dear community I am having troule to collect metrics after runing mini-ndn experiments I noticed tho following work: http://2nd-ndn-hackathon.named-data.net/mini-ndn-metrics/ It seems interesting, unfortunately there is no documentation on how building and using it can anybody help? best regards -- Nour El Houda Ben Youssef Koub?a PhD student Mobidoc - WEVIOO/SAGE/ENSI Master degree New Generation of Information Systems - FST Software Engineer - INSAT -------------- next part -------------- An HTML attachment was scrubbed... URL: From nou.mail at gmail.com Mon Jan 23 23:52:44 2017 From: nou.mail at gmail.com (Nour El Houda Ben Youssef) Date: Tue, 24 Jan 2017 08:52:44 +0100 Subject: [Mini-NDN] metric collection In-Reply-To: References: Message-ID: I deployed a traffic generator that periodically issue interests while producer nodes generate the content I would like then to compute interest satisfaction delay I want also to compute overhead (with HR and Lsr) and timeout interests if any Best regards On Jan 24, 2017 12:15 AM, "Ashlesh Gawande (agawande)" wrote: > What specific metrics are you having trouble collecting? > > > That was a part of a hackathon effort of 1-2 days and hence lacks any > documentation. > > > The lead of that hackathon project has left our group so I do not have any > information on it. Best would be to just go through the code that was added > using git and try to figure it out. > > > Ashlesh > ------------------------------ > *From:* Mini-NDN on behalf of Nour > El Houda Ben Youssef > *Sent:* Monday, January 23, 2017 1:46 AM > *To:* mini-ndn at lists.cs.ucla.edu > *Subject:* [Mini-NDN] metric collection > > Dear community > > I am having troule to collect metrics after runing mini-ndn experiments > > I noticed tho following work: > http://2nd-ndn-hackathon.named-data.net/mini-ndn-metrics/ > > It seems interesting, unfortunately there is no documentation on how > building and using it > > can anybody help? > > best regards > > -- > Nour El Houda Ben Youssef Koub?a > PhD student Mobidoc - WEVIOO/SAGE/ENSI > Master degree New Generation of Information Systems - FST > Software Engineer - INSAT > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nou.mail at gmail.com Mon Jan 23 23:53:45 2017 From: nou.mail at gmail.com (Nour El Houda Ben Youssef) Date: Tue, 24 Jan 2017 08:53:45 +0100 Subject: [Mini-NDN] metric collection In-Reply-To: References: Message-ID: I deployed a traffic generator that periodically issue interests while producer nodes generate desired content I would like then to compute interest satisfaction delay, network throughput, overhead (for LSR and HR) and timedout interests if any Best regards On Jan 24, 2017 12:15 AM, "Ashlesh Gawande (agawande)" wrote: > What specific metrics are you having trouble collecting? > > > That was a part of a hackathon effort of 1-2 days and hence lacks any > documentation. > > > The lead of that hackathon project has left our group so I do not have any > information on it. Best would be to just go through the code that was added > using git and try to figure it out. > > > Ashlesh > ------------------------------ > *From:* Mini-NDN on behalf of Nour > El Houda Ben Youssef > *Sent:* Monday, January 23, 2017 1:46 AM > *To:* mini-ndn at lists.cs.ucla.edu > *Subject:* [Mini-NDN] metric collection > > Dear community > > I am having troule to collect metrics after runing mini-ndn experiments > > I noticed tho following work: > http://2nd-ndn-hackathon.named-data.net/mini-ndn-metrics/ > > It seems interesting, unfortunately there is no documentation on how > building and using it > > can anybody help? > > best regards > > -- > Nour El Houda Ben Youssef Koub?a > PhD student Mobidoc - WEVIOO/SAGE/ENSI > Master degree New Generation of Information Systems - FST > Software Engineer - INSAT > -------------- next part -------------- An HTML attachment was scrubbed... URL: From agawande at memphis.edu Wed Jan 25 07:40:09 2017 From: agawande at memphis.edu (Ashlesh Gawande (agawande)) Date: Wed, 25 Jan 2017 15:40:09 +0000 Subject: [Mini-NDN] metric collection In-Reply-To: References: , Message-ID: You can turn on ndndump on all the nodes: for host in net.hosts: for intf in host.intfNames(): ndnDumpOutputFile = "dump.%s" % intf host.cmd("sudo ndndump -i %s > %s &" % (intf, ndnDumpOutputFile)) You can use the iperf command for network characteristics: (example: https://github.com/mininet/mininet/blob/master/examples/intfoptions.py) For timeouts and overhead of LS and HR you can count the sync messages in the ndndump. ________________________________ From: Nour El Houda Ben Youssef Sent: Tuesday, January 24, 2017 1:53:45 AM To: Ashlesh Gawande (agawande) Cc: mini-ndn at lists.cs.ucla.edu Subject: Re: [Mini-NDN] metric collection I deployed a traffic generator that periodically issue interests while producer nodes generate desired content I would like then to compute interest satisfaction delay, network throughput, overhead (for LSR and HR) and timedout interests if any Best regards On Jan 24, 2017 12:15 AM, "Ashlesh Gawande (agawande)" > wrote: What specific metrics are you having trouble collecting? That was a part of a hackathon effort of 1-2 days and hence lacks any documentation. The lead of that hackathon project has left our group so I do not have any information on it. Best would be to just go through the code that was added using git and try to figure it out. Ashlesh ________________________________ From: Mini-NDN > on behalf of Nour El Houda Ben Youssef > Sent: Monday, January 23, 2017 1:46 AM To: mini-ndn at lists.cs.ucla.edu Subject: [Mini-NDN] metric collection Dear community I am having troule to collect metrics after runing mini-ndn experiments I noticed tho following work: http://2nd-ndn-hackathon.named-data.net/mini-ndn-metrics/ It seems interesting, unfortunately there is no documentation on how building and using it can anybody help? best regards -- Nour El Houda Ben Youssef Koub?a PhD student Mobidoc - WEVIOO/SAGE/ENSI Master degree New Generation of Information Systems - FST Software Engineer - INSAT -------------- next part -------------- An HTML attachment was scrubbed... URL: From nou.mail at gmail.com Wed Jan 25 23:38:43 2017 From: nou.mail at gmail.com (Nour El Houda Ben Youssef) Date: Thu, 26 Jan 2017 08:38:43 +0100 Subject: [Mini-NDN] metric collection In-Reply-To: References: Message-ID: Thanks It's been very helpful On Jan 25, 2017 4:40 PM, "Ashlesh Gawande (agawande)" wrote: > You can turn on ndndump on all the nodes: > > for host in net.hosts: > for intf in host.intfNames(): > ndnDumpOutputFile = "dump.%s" % intf > host.cmd("sudo ndndump -i %s > %s &" % (intf, > ndnDumpOutputFile)) > > You can use the iperf command for network characteristics: > (example: https://github.com/mininet/mininet/blob/master/ > examples/intfoptions.py) > > For timeouts and overhead of LS and HR you can count the sync messages in > the ndndump. > > ------------------------------ > *From:* Nour El Houda Ben Youssef > *Sent:* Tuesday, January 24, 2017 1:53:45 AM > *To:* Ashlesh Gawande (agawande) > *Cc:* mini-ndn at lists.cs.ucla.edu > *Subject:* Re: [Mini-NDN] metric collection > > > I deployed a traffic generator that periodically issue interests while > producer nodes generate desired content > > > I would like then to compute interest satisfaction delay, network > throughput, overhead (for LSR and HR) and timedout interests if any > > Best regards > > > > On Jan 24, 2017 12:15 AM, "Ashlesh Gawande (agawande)" < > agawande at memphis.edu> wrote: > >> What specific metrics are you having trouble collecting? >> >> >> That was a part of a hackathon effort of 1-2 days and hence lacks any >> documentation. >> >> >> The lead of that hackathon project has left our group so I do not have >> any information on it. Best would be to just go through the code that was >> added using git and try to figure it out. >> >> >> Ashlesh >> ------------------------------ >> *From:* Mini-NDN on behalf of Nour >> El Houda Ben Youssef >> *Sent:* Monday, January 23, 2017 1:46 AM >> *To:* mini-ndn at lists.cs.ucla.edu >> *Subject:* [Mini-NDN] metric collection >> >> Dear community >> >> I am having troule to collect metrics after runing mini-ndn experiments >> >> I noticed tho following work: >> http://2nd-ndn-hackathon.named-data.net/mini-ndn-metrics/ >> >> It seems interesting, unfortunately there is no documentation on how >> building and using it >> >> can anybody help? >> >> best regards >> >> -- >> Nour El Houda Ben Youssef Koub?a >> PhD student Mobidoc - WEVIOO/SAGE/ENSI >> Master degree New Generation of Information Systems - FST >> Software Engineer - INSAT >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nou.mail at gmail.com Thu Jan 26 02:56:56 2017 From: nou.mail at gmail.com (Nour El Houda Ben Youssef) Date: Thu, 26 Jan 2017 11:56:56 +0100 Subject: [Mini-NDN] logging results mismatch Message-ID: Dear community thank you in advance for the help that I'am getting from you After running few experimentations, I noticed results mismatch For instance ndn-traffic-generator log file indicates that 10 interests for a certain prefix has been sent and corresponding data has been received when I consult ndndump file of the node expressing interests, I only find 2 interests of this prefix does logging with ndndump take much longer than ndn-traffic-generator logging? How much time do you think I should wait to be sure that scheduled data flows in my experiment were performed in order to process my logfile and extract final results? best regards -- Nour El Houda Ben Youssef Koub?a PhD student Mobidoc - WEVIOO/SAGE/ENSI Master degree New Generation of Information Systems - FST Software Engineer - INSAT -------------- next part -------------- An HTML attachment was scrubbed... URL: From agawande at memphis.edu Thu Jan 26 07:53:00 2017 From: agawande at memphis.edu (Ashlesh Gawande (agawande)) Date: Thu, 26 Jan 2017 15:53:00 +0000 Subject: [Mini-NDN] logging results mismatch In-Reply-To: References: Message-ID: When do you start ndndump? Start it before you run the ndn-traffic-generator. Then when your experiment ends all the interest/data should be there in ndndump - you don't need to give any extra time. Also there are multiple dump files for each interface of the node. Ashlesh ________________________________ From: Mini-NDN on behalf of Nour El Houda Ben Youssef Sent: Thursday, January 26, 2017 4:56:56 AM To: mini-ndn at lists.cs.ucla.edu Subject: [Mini-NDN] logging results mismatch Dear community thank you in advance for the help that I'am getting from you After running few experimentations, I noticed results mismatch For instance ndn-traffic-generator log file indicates that 10 interests for a certain prefix has been sent and corresponding data has been received when I consult ndndump file of the node expressing interests, I only find 2 interests of this prefix does logging with ndndump take much longer than ndn-traffic-generator logging? How much time do you think I should wait to be sure that scheduled data flows in my experiment were performed in order to process my logfile and extract final results? best regards -- Nour El Houda Ben Youssef Koub?a PhD student Mobidoc - WEVIOO/SAGE/ENSI Master degree New Generation of Information Systems - FST Software Engineer - INSAT -------------- next part -------------- An HTML attachment was scrubbed... URL: From nou.mail at gmail.com Fri Jan 27 01:04:35 2017 From: nou.mail at gmail.com (Nour El Houda Ben Youssef) Date: Fri, 27 Jan 2017 10:04:35 +0100 Subject: [Mini-NDN] HR coordinates Message-ID: Dear community I would like to compare HR and LSR performances in my particular topology built under mini-ndn if I got HR rationale well, Hyperbolic coordinates needs to be assigned to prefixes, in that case why are we assinging them to nodes instead ? How do we compute nodes coordinates? how to turn on HR? I think it has to be done in topology.config file but is there any topology.config specification to help us write correct config files? In order to tune forwardig strategies does it have to be done in NFD config file ? thank you -- Nour El Houda Ben Youssef Koub?a PhD student Mobidoc - WEVIOO/SAGE/ENSI Master degree New Generation of Information Systems - FST Software Engineer - INSAT -------------- next part -------------- An HTML attachment was scrubbed... URL: From nou.mail at gmail.com Mon Jan 30 00:37:51 2017 From: nou.mail at gmail.com (Nour El Houda Ben Youssef) Date: Mon, 30 Jan 2017 09:37:51 +0100 Subject: [Mini-NDN] HR in mini-ndn overhead messages Message-ID: Dear community I was trying to evaluate overhead under various forwarding/ routing strategies in mini-ndn with NLSR /best-route combination LSA/sync packets are used to compute overhead with HR/ASF which packets are used to compute overhead, as ndndump files were analyzed no probing packets were found ! best regards -- Nour El Houda Ben Youssef Koub?a PhD student Mobidoc - WEVIOO/SAGE/ENSI Master degree New Generation of Information Systems - FST Software Engineer - INSAT -------------- next part -------------- An HTML attachment was scrubbed... URL: From agawande at memphis.edu Mon Jan 30 07:16:24 2017 From: agawande at memphis.edu (Ashlesh Gawande (agawande)) Date: Mon, 30 Jan 2017 15:16:24 +0000 Subject: [Mini-NDN] HR in mini-ndn overhead messages In-Reply-To: References: Message-ID: What we did was to set the Nonce of ndnping to zero and count all non-zero Nonce as probing overhead for HR. Because there was no other way to distinguish. You may also set the Nonce of the probe to some special value here instead of calling refreshNonce: https://github.com/named-data/NFD/blob/master/daemon/fw/asf-strategy.cpp#L158 To answer your other questions: There are some sample topologies on how to set the coordinates: https://github.com/named-data/mini-ndn/blob/master/ndn_utils/topologies/minindn.ucla.conf Any prefix under that node would be reached via that node's coordinates (i.e. the distance would be calculated based on that node's coordinates). To turn on the hyperbolic routing simply use the option --hr which configures this section of nlsr.conf: https://github.com/named-data/NLSR/blob/master/nlsr.conf#L93 In order to tune the forwarding strategies you can look into the newly introduced Strategy Parameters: https://redmine.named-data.net/issues/3868 Or you can directly change NFD and recompile, reinstall NFD - but thats not convenient. Ashlesh ________________________________ From: Mini-NDN on behalf of Nour El Houda Ben Youssef Sent: Monday, January 30, 2017 2:37:51 AM To: mini-ndn at lists.cs.ucla.edu Subject: [Mini-NDN] HR in mini-ndn overhead messages Dear community I was trying to evaluate overhead under various forwarding/ routing strategies in mini-ndn with NLSR /best-route combination LSA/sync packets are used to compute overhead with HR/ASF which packets are used to compute overhead, as ndndump files were analyzed no probing packets were found ! best regards -- Nour El Houda Ben Youssef Koub?a PhD student Mobidoc - WEVIOO/SAGE/ENSI Master degree New Generation of Information Systems - FST Software Engineer - INSAT -------------- next part -------------- An HTML attachment was scrubbed... URL: From nou.mail at gmail.com Mon Jan 30 12:44:03 2017 From: nou.mail at gmail.com (Nour El Houda Ben Youssef) Date: Mon, 30 Jan 2017 21:44:03 +0100 Subject: [Mini-NDN] HR in mini-ndn overhead messages In-Reply-To: References: Message-ID: thank you Ashlesh for your precious support On Mon, Jan 30, 2017 at 4:16 PM, Ashlesh Gawande (agawande) < agawande at memphis.edu> wrote: > What we did was to set the Nonce of ndnping to zero and count all non-zero > Nonce as probing overhead for HR. Because there was no other way to > distinguish. > > You may also set the Nonce of the probe to some special value here instead > of calling refreshNonce: > > https://github.com/named-data/NFD/blob/master/daemon/fw/asf- > strategy.cpp#L158 > > > To answer your other questions: > > There are some sample topologies on how to set the coordinates: > > https://github.com/named-data/mini-ndn/blob/master/ndn_ > utils/topologies/minindn.ucla.conf > > Any prefix under that node would be reached via that node's coordinates > (i.e. the distance would be calculated based on that node's coordinates). > > > To turn on the hyperbolic routing simply use the option --hr which > configures this section of nlsr.conf: > > https://github.com/named-data/NLSR/blob/master/nlsr.conf#L93 > > > In order to tune the forwarding strategies you can look into the newly > introduced Strategy Parameters: > > https://redmine.named-data.net/issues/3868 > > Or you can directly change NFD and recompile, reinstall NFD - but thats > not convenient. > > > Ashlesh > ------------------------------ > *From:* Mini-NDN on behalf of Nour > El Houda Ben Youssef > *Sent:* Monday, January 30, 2017 2:37:51 AM > *To:* mini-ndn at lists.cs.ucla.edu > *Subject:* [Mini-NDN] HR in mini-ndn overhead messages > > Dear community > > I was trying to evaluate overhead under various forwarding/ routing > strategies in mini-ndn > > with NLSR /best-route combination LSA/sync packets are used to compute > overhead > > with HR/ASF which packets are used to compute overhead, as ndndump files > were analyzed no probing packets were found ! > > best regards > > -- > Nour El Houda Ben Youssef Koub?a > PhD student Mobidoc - WEVIOO/SAGE/ENSI > Master degree New Generation of Information Systems - FST > Software Engineer - INSAT > -- Nour El Houda Ben Youssef Koub?a PhD student Mobidoc - WEVIOO/SAGE/ENSI Master degree New Generation of Information Systems - FST Software Engineer - INSAT -------------- next part -------------- An HTML attachment was scrubbed... URL: