INET4.1.0: EtherAppServer and end-to-end-delay statistic

[amrcg]

Hello,

Any good reason to have dropped the end-to-end-delay histogram from the statistics of EtherAppServer? Or better: the statistic is there in the .ned file, it always returns NaN.

Best regards,

António Grilo

[amrcg]

Bingo!

In the EtherAppServer.ned file, the source of the end-to-end-delay statistic must be changed from "dataAge" to "messageAge", as it was in the previous versions.

Regards,

António

[Levente Mészáros]

Actually, the messageAge filter calculates the elapsed time since the packet was created. Unfortunately, a packet received by the server may have been created in the underlying network anywhere for whatever reason. In the INET 4.x branch, the end-to-end delay is calculated from the timestamp attached to the data (chunks) as a region tag instead of from a timestamp attached to the whole packet as packet tag. See here:

https://inet.omnetpp.org/docs/developers-guide/ch-packets.html#region-tagging

In the simple ethernet frame case, the two should give the same result. If the statistic doesn't show up with dataAge, then either the client doesn't set the tag or it gets deleted somewhere on the way to the server.

Regards,

levy

--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.