Changes between Version 8 and Version 9 of TmixDetails


Ignore:
Timestamp:
10/19/12 11:53:54 (11 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TmixDetails

    v8 v9  
    33
    44== The a-b-t Model ==
    5 A TCP/IP header trace is obtained from a real-world link, and is then "reverse compiled" into a higher-level representation.  For every TCP/IP connection in the trace a connection vector is generated.  The connection vector represents an entire single connection between "''a''", the connection initiator, and "''b''", the connection accepter.  Rather than modeling the individual packets or TCP segments, Tmix instead uses inferences to characterize connections as a sequence of request-response exchanges between "''a''" and "''b''".  Each request or response transfers one application-data unit (ADU), which is a generic term for the object or protocol element being transferred.   Further, each exchange (request then response) is called an epoch, and includes the sizes of the ADUs transferred, and the requester side "think" or processing time, "''t''".  More formally, a simulation would consist of a set of ''n'' connection vectors ''C'',,1...''n'',,, each including a set of ''k'' epochs, ''C'',,''i'',,=<''E'',,1,,,''E'',,2,,,..., ''E'',,k>, where each epoch is defined by ''E'' .
     5A TCP/IP header trace is obtained from a real-world link, and is then "reverse compiled" into a higher-level representation.  For every TCP/IP connection in the trace a connection vector is generated.  The connection vector represents an entire single connection between "''a''", the connection initiator, and "''b''", the connection accepter.  Rather than modeling the individual packets or TCP segments, Tmix instead uses inferences to characterize connections as a sequence of request-response exchanges between "''a''" and "''b''".  Each request or response transfers one application-data unit (ADU), which is a generic term for the object or protocol element being transferred.   Further, each exchange (request then response) is called an epoch, and includes the sizes of the ADUs transferred, and the requester side "think" or processing time, "''t''".  More formally, a simulation would consist of a set of ''n'' connection vectors ''C'',,1...''n'',,, each including a set of ''k'' epochs, ''C'',,''i'',,=<''E'',,1,,,''E'',,2,,,..., ''E'',,k,,>, where each epoch is defined by ''E,,i,,'' = (''a,,i,,'',''b,,i,,'',''t,,i,,'').
    66
    77where each epoch includes ''a'',,''i'',,, the size of the ''i''^th^ ADU sent f