[Mini-NDN] [EXT] About the Traffic Generator, nHits, nMissed and nEntries

Leanna Vidya Yovita leanna.vidya at gmail.com
Mon Mar 1 15:14:15 PST 2021


Dear Junxiao,
Alright, I get it. Thank you so much for the explanation.


Regards,
Leanna

On Mon, Mar 1, 2021 at 10:43 PM Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Leanna
>
> ndn-traffic-client doesn't support any other traffic patterns.
> According to git history, its last feature update was 2019-January. After
> that, there's only passive maintenance. Moreover, most of its features are
> duplicate of ndnping.
>
> You could, however, use ndnping to create some Interests that can
> potentially result in cache hits. The method is starting two instances of
> ndnping at the same time with the *-a -n* flags.
> I used a similar technique in the Content Store evaluation of the NDN-DPDK
> paper, although the program isn't ndnping.
>
> Yours, Junxiao
>
> On Mon, Mar 1, 2021, 01:29 Leanna Vidya Yovita <leanna.vidya at gmail.com>
> wrote:
>
>> *External Email*
>> Dear Junxiao,
>> thank you for the explanation.
>> I understand now.
>> Related to my question no.4, ndn-traffic-client appends a sequence
>> number, so that the content is actually different.
>> Is it possible sometimes the client request the same content? how to
>> control it? I mean, can we control the distribution of client's request?
>> such as follow Zipf for exactly total X number of content/document?
>> it is needed to analyze the result.
>>
>> Thank you in advance.
>>
>> regards,
>> Leanna
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20210302/a6503dd9/attachment.html>


More information about the Mini-NDN mailing list