Changes between Version 22 and Version 23 of TmixDetails


Ignore:
Timestamp:
10/19/12 13:09:17 (7 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TmixDetails

    v22 v23  
    1111== Workload Generation ==
    1212
    13 At run-time Tmix "replays" the exchanges encoded in the set of connection vectors.  Tmix is simultaneously run on two machines, each at the edge of a test network.  One machine plays the role of initiator, while the other is the acceptor.    For each connection vector a TCP connection is established from the initiator to the acceptor at time ''T,,i,,''.  The initiator then performs socket writes to send ''a,,1,,'' bytes (the size of the "request" ADU of epoch 1) of fake data.  At the same time, Tmix on the acceptor reads the same number of bytes from it's associated socket.  The roles then reverse with the acceptor sending a "response" of ''b,,1,,'' bytes back to the initiator, while it reads them.  The initiator then sleeps for ''t,,i,,'' seconds before sending the next "request".  The last epoch of a connection doesn't contain a "think" time, and when it is reached the connection is terminated. 
     13At run-time Tmix "replays" the exchanges encoded in the set of connection vectors.  Tmix is simultaneously run on two machines, each at the edge of a test network.  One machine plays the role of initiator, while the other is the acceptor.    For each connection vector a TCP connection is established from the initiator to the acceptor at time ''T,,i,,''.  The initiator then performs socket writes to send ''a,,1,,'' bytes (the size of the "request" ADU of epoch 1) of fake data.  At the same time, Tmix on the acceptor reads the same number of bytes from it's associated socket.  The roles then reverse with the acceptor sending a "response" of ''b,,1,,'' bytes back to the initiator, while it reads them.  The initiator then sleeps for ''t,,i,,'' seconds before looping and sending the next "request".  This process continues until the last epoch of a connection, which doesn't include a "think" time, is reached.  The connection is then terminated.