<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Junxiao,</p>
<p><br>
</p>
<p>that makes sense, thanks for the help so far. <br>
</p>
<p><br>
</p>
<p>I looked into the ndnping example but one doubt remains. What if
I want to consume large chunks of data, say 10MB or more. In this
case, I will need to divide that into chunks of 8800 bytes at
most, since that is the maximum NDN package size allowed. However,
using the same mechanism as ndnping or
consumer/consumer-with-timer, the program would have to wait until
one 8800 B package is received before requesting the next one
(using face.expressInterest). How can I do that so that I don`t
have to wait a full round-trip-time before consuming the next
part?</p>
<p><br>
</p>
<p>Best regards,</p>
<p>André<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 20/04/2021 01:07, Junxiao Shi wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAOFH+OY2gXPX-V_wkcuhoiUmPt4igJyrq8CEnBguzGT1Pkmt2g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi André</div>
<div><br>
</div>
<div>The number of faces in an application should be O(1).</div>
<div>If you have O(N) or O(log N) faces, you are doing it wrong.<br>
</div>
<div><br>
</div>
Most applications only have one or two faces.
<div>You can send and receive multiple packets through the same
face.<br>
</div>
<div><br>
</div>
<div>Yours, Junxiao<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Apr 19, 2021 at
10:47 PM André Dexheimer <<a
href="mailto:adcarneiro@inf.ufrgs.br"
moz-do-not-send="true">adcarneiro@inf.ufrgs.br</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<p style="text-align:center"><font color="red"><b>External
Email</b><br>
</font></p>
<div dir="auto">
<div>Hello Junxiao</div>
<div dir="auto"><br>
</div>
<div dir="auto">Thank you for the quick response.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I have 6 CPU cores and 12GB of RAM
allocated to the virtual machine. </div>
<div dir="auto"><br>
</div>
<div dir="auto">The consumer-with-timer was slightly
modified to schedule a variable number of consumer
requests at a variable period.</div>
<div dir="auto"><br>
</div>
<div dir="auto">How would you suggest that I instantiate
the faces to reduce overhead? Maybe create an array of
faces so that I don't have to wait for each packet to
arrive before I request the next one?</div>
<div dir="auto"><br>
</div>
<div dir="auto">Best regard,</div>
<div dir="auto">Andre<br>
<div class="gmail_extra" dir="auto"><br>
<div class="gmail_quote">On Apr 19, 2021 22:48,
Junxiao Shi <<a
href="mailto:shijunxiao@email.arizona.edu"
target="_blank" moz-do-not-send="true">shijunxiao@email.arizona.edu</a>>
wrote:<br type="attribution">
<blockquote style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Hi Andre</div>
<div><br>
</div>
<div>How much hardware resources did you
allocate to the topology?</div>
<div>Since you have 8 nodes, you need at least 8
CPU cores and 8GB RAM for a smooth operation.<br>
</div>
<div><br>
</div>
<div>If you are using
ndn-cxx/examples/consumer-with-timer.cpp
unchanged: each invocation of this program
sends 2 Interests, and then the program exits.<br>
</div>
<div>Forking and joining all those short-lived
processes, as well as NFD accepting and
closing the faces, would cause significant
overhead.</div>
<div>You should instead use a long-lived
consumer program, such as the ndnping client.<br>
</div>
<div><br>
</div>
<div>Yours, Junxiao<br>
</div>
</div>
<br>
<div>
<div dir="ltr">On Mon, Apr 19, 2021 at 9:36 PM
Andre via Mini-NDN <<a
href="mailto:mini-ndn@lists.cs.ucla.edu"
target="_blank" moz-do-not-send="true">mini-ndn@lists.cs.ucla.edu</a>>
wrote:<br>
</div>
<blockquote style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>
<p style="text-align:center"><font
color="red"><b>External Email</b><br>
</font></p>
<p> Hi</p>
<p><br>
</p>
<p>I am running a simple experiment
generating traffic between nodes in the
following topology, where all links have
10ms delay and 10mbits/s of bandwidth.<br>
</p>
<p><br>
</p>
<p><img alt="" moz-do-not-send="true"></p>
<p><br>
</p>
<p>I am running the default producer and
consumer-with-timer from the ndn-cxx
examples to randomly generate traffic flow
between nodes. I am having an issue where,
after a few seconds of only successful
transfers, every consumer starts timing
out on every request. <br>
</p>
<p>When each consumer requests a packet
every 100 milliseconds, I get about 20
timeouts for every successful transfer. As
I raise this period, things get better and
by a period of 1 second, I get no
timeouts. So it seems that there is some
limitation to how much can be consumed or
produced.</p>
<p>So I am wondering, why does this happen?
Is it a limitation of the consumer or the
producer from ndn-cxx? Or is it related to
the network emulation?</p>
<p><br>
</p>
<p>Thanks in advance,</p>
<p>André Dexheimer Carneiro<br>
</p>
<p><br>
</p>
<p><br>
</p>
</div>
_______________________________________________<br>
Mini-NDN mailing list<br>
<a href="mailto:Mini-NDN@lists.cs.ucla.edu"
target="_blank" moz-do-not-send="true">Mini-NDN@lists.cs.ucla.edu</a><br>
<a
href="http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn"
target="_blank" moz-do-not-send="true">http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn</a><br>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</body>
</html>