[ndnSIM] app-delays-trace.txt

Spyridon (Spyros) Mastorakis mastorakis at CS.UCLA.EDU
Thu Dec 22 23:06:00 PST 2016


Hi,

I am not aware of the exact parameters of your simulation scenario, but most probably this has to do with either the simulation topology itself or the topology parameters (bandwidth, queue length at each node and delay). Another reason could be the rate that the consumers send their Interests.

Spyridon (Spyros) Mastorakis
Personal Website: http://cs.ucla.edu/~mastorakis/ <http://cs.ucla.edu/~mastorakis/>
Internet Research Laboratory
Computer Science Department
UCLA

> On Dec 23, 2016, at 4:18 AM, 任沛 <renpei.bupt at qq.com> wrote:
> 
> Dear all,
>   I use the "AppDelayTracer" in a scenario which topology same like load balancing in the given example, and then get a txt named app-delays-trace, there is one consumer and three producers, while DelaysUS is not the same number, who can explain difference between these number? why they are different? part of DelaysUS is show bellow:
> 98448
> 98448
> 98000
> 98448
> 98000
> 98448
> 98448
> 98448
> 98448
> 98448
> 98000
> 98448
> 98448
> 98000
> 98000
> 98448
> ...
> 98480
> 98032
> 98480
> 98032
> 98480
> 98480
> 98480
> there exist three numbers 98000 98032 and 98448
> I'm really appreciate if anyone can help me.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20161223/5c2183c5/attachment-0001.html>


More information about the ndnSIM mailing list