<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Saeid,<div><br></div><div>I haven't used MPI, I just run different runs/scenarios in parallel (using ./run.py script, which in current form runs as many instances as the number of CPUs). I don't quite remember the exact timeline, I think it was about two days with 32 CPUs to finish all simulation runs for 4 different scenarios.</div><div><br></div><div>---</div><div>Alex</div><div><br><div><div>On Jul 1, 2013, at 10:00 PM, Saeid Montazeri <<a href="mailto:saeid.montazeri@gmail.com">saeid.montazeri@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Dear Alex,<div><br></div><div>Thanks a lot for the reply. May I have an estimate of the execution time of the Interest Flooding scenario (Please let me know the simulation time). Did you use MPI? If yes what was the number of processes?</div>
<div><br></div><div>Best Regards,</div><div>Saeid<br><br><div class="gmail_quote">On Tue, Jul 2, 2013 at 1:20 AM, Alex Afanasyev <span dir="ltr"><<a href="mailto:alexander.afanasyev@ucla.edu" target="_blank">alexander.afanasyev@ucla.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi Saeid,<div><br></div><div>We have used Abilene topology, including link delays in <a href="https://github.com/cawka/ndnSIM-comcom-stateful-fw" target="_blank">https://github.com/cawka/ndnSIM-comcom-stateful-fw</a>. </div>
<div><br></div><div>Since Abilene topology is provided in several files, here is an example how to read it:</div><div><br></div><div><pre style="font-family:Consolas,'Liberation Mono',Courier,monospace;font-size:13px;margin-top:0px;margin-bottom:0px;color:rgb(51,51,51);line-height:18px"><div style="padding-left:10px"><span> RocketfuelWeightsReader</span> <span>rf_reader;</span></div><div style="padding-left:10px"> <span>string</span> <span style="color:rgb(153,0,0);font-weight:bold">weights</span> <span>(</span><span>topology</span><span style="font-weight:bold">+</span><span style="color:rgb(221,17,68)">".weights"</span><span>);</span></div>
<div style="padding-left:10px"> <span>string</span> <span style="color:rgb(153,0,0);font-weight:bold">latencies</span> <span>(</span><span>topology</span><span style="font-weight:bold">+</span><span style="color:rgb(221,17,68)">".latencies"</span><span>);</span></div>
<div style="padding-left:10px"><br></div><div style="padding-left:10px"> <span>rf_reader<b>.</b></span><span>SetFileName</span> <span>(</span><span>weights</span><span>);</span></div><div style="padding-left:10px"> <span>rf_reader<b>.</b></span><span>SetFileType</span> <span>(</span><span>RocketfuelWeightsReader</span><span style="font-weight:bold">::</span><span>WEIGHTS</span><span>);</span></div>
<div style="padding-left:10px"> <span>rf_reader<b>.</b></span><span>Read</span> <span>();</span></div><div style="padding-left:10px"><br></div><div style="padding-left:10px"> <span>rf_reader<b>.</b></span><span>SetFileName</span> <span>(</span><span>latencies</span><span>);</span></div>
<div style="padding-left:10px"> <span>rf_reader<b>.</b></span><span>SetFileType</span> <span>(</span><span>RocketfuelWeightsReader</span><span style="font-weight:bold">::</span><span>LATENCIES</span><span>);</span></div>
<div style="padding-left:10px"> <span>rf_reader<b>.</b></span><span>Read</span> <span>();</span></div></pre><div><br></div></div><div><br></div><div>As for your first question. I would say that the choice really depends on what exactly you're simulating. Abilene topology (if you're talking about the core topology) is really small and you don't have too much choice, even for random. In Interest Flooding simulation (<a href="https://github.com/cawka/ndnSIM-ddos-interest-flooding" target="_blank">https://github.com/cawka/ndnSIM-ddos-interest-flooding</a>) we have used larger topology from RocketFuel (unfortunately no real link delays or bandwidths, but we did some randomization for that), where we selected different tiers of nodes based on their topological parameters (leaf nodes are customers, next level are gateways, the rest is a backbone) and then installed consumers on random subset of leaf nodes. Depending on where producer is installed (leaf, gw, backbone), you can get different results, as well as different real world scenario that it could represent.</div>
<div><br></div><div>Hope it helps.</div><div><br></div><div>---</div><div>Alex</div><div><br><div><div><div class="h5"><div>On Jul 1, 2013, at 1:12 AM, Saeid Montazeri <<a href="mailto:saeid.montazeri@gmail.com" target="_blank">saeid.montazeri@gmail.com</a>> wrote:</div>
<br></div></div><blockquote type="cite"><div><div class="h5">Dear All,<div><br></div><div>I am going to use abilene topology for my evaluation. I have a question:</div><div>How should I distribute the consumers and producers in the topology. Obviously, the simplest way is random. However, I am thinking about something more reasonable!</div>
<div><br></div><div>Meanwhile, it will be really helpful to have a reference for the link delay of the topology since the ndnSIM version does not have the link delays. </div><div><br></div><div>Best Regards,</div><div>Saeid</div>
</div></div>
_______________________________________________<br>ndnSIM mailing list<br><a href="mailto:ndnSIM@lists.cs.ucla.edu" target="_blank">ndnSIM@lists.cs.ucla.edu</a><br><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim" target="_blank">http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim</a><br>
</blockquote></div><br></div></div></blockquote></div><br></div>
_______________________________________________<br>ndnSIM mailing list<br><a href="mailto:ndnSIM@lists.cs.ucla.edu">ndnSIM@lists.cs.ucla.edu</a><br>http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim<br></blockquote></div><br></div></body></html>