Inter-flow delay

[Carter Bullard]

Hey Sebas 
I had the definitions the other way around...

>>> Is it f2.startime - f1.startime ??   Flow arrival delay
>>> Is it f2.startime - f1.lasttime ??   Interflow idle time

The first one is the flow / transaction arrival time, flow arrival delay, first derivative of the flow start time(s).   ( 1 / mean(flow arrival time) )  is the transaction arrival rate.  This is a very big metric.  

The interflow idle time, (f2.startime - f1.endtime) is an important occupancy metric, as it helps to describe a specific flows cache demand, and general network demand.

Carter

> On Mar 26, 2014, at 5:13 AM, el draco <eldraco at gmail.com> wrote:
> 
> Yes I'm also using f2.starttime - f1.starttime too.
> 
> However, if you implement this, I'm not sure if the name for this metric should be Interflow Idle time, because it includes the first flow completely, right?
> 
> So    f2.starttime - f1.endtime = Flow arrival delay, or time between the end of the first flow and the start of the second. No data on the network.
> And f2.starttime - f1.starttime = Includes the duration of the first flow plus the flow arrival delay. For a moment there is data on the network. Not sure if Interflow idle time is correct here. Maybe "Interflow start time"?
> 
> thanks
> sebas
> 
> 
>  
> 
> 
>> On Wed, Mar 19, 2014 at 7:17 PM, Rahimeh Khodadadi <rahimeh.khodadadi at gmail.com> wrote:
>> Hi Carter and Sebas,
>> 
>> Thanks for your response, yes I did this work by f2.startime - f1.startime.
>> 
>> Thanks again.
>> Rahimeh
>> 
>> 
>>> On Wed, Mar 19, 2014 at 9:31 PM, Carter Bullard <carter at qosient.com> wrote:
>>> Hey Rahimeh and Sebas,
>>> What is the definition of this metric ???
>>> 
>>> Is it f2.startime - f1.startime ??   Flow arrival delay
>>> Is it f2.startime - f1.lasttime ??   Interflow idle time
>>> 
>>> We have these abstractions in the jitter aggregation methods,
>>> so it wouldn’t be hard to do, but it will have to be after
>>> 3.0.8.  As Sebas indicates, its easy to calculate these
>>> outside argus.
>>> 
>>> Carter
>>> 
>>>> On Mar 19, 2014, at 10:10 AM, el draco <eldraco at gmail.com> wrote:
>>>> 
>>>> Hi Rahimeh, sorry for the delay.
>>>> As far as I know there is no support in Argus yet for inter-flow timing. However, it should be possible to do it if you cluster the flows with racluster. 
>>>> Some time ago we discussed about this here.
>>>> I also need that information and I'm processing the argus output with a custom python program to get this data.
>>>> 
>>>> sebas
>>>> 
>>>> 
>>>>> On Thu, Jan 30, 2014 at 5:21 PM, Rahimeh Khodadadi <rahimeh.khodadadi at gmail.com> wrote:
>>>>> Hi, 
>>>>> 
>>>>> I have a question, can I get inter-flow delay for every flow of every ip addresses in Argus?
>>>>> 
>>>>> I will be glad, if you help me.
>>>>> 
>>>>> Thanks in advance,
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20140326/9d099acf/attachment.html>