Changes between Version 59 and Version 60 of GeniTmixCalibTutorial


Ignore:
Timestamp:
06/19/14 20:45:28 (5 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTmixCalibTutorial

    v59 v60  
    5050}}}
    5151
    52 2.  '''Edit the tmix.conf''' file using a terminal text editor such that your Crecv and Cinit lines are the following. 
     522.  '''Repeat''' for the other node. 
     53
     543.  '''Edit the tmix.conf''' file on both nodes using a terminal text editor such that your Crecv and Cinit lines are the following. 
    5355{{{
    5456Cinit_Trace = /opt/tmix-1.2/data/1of10.cinit.tcvec
     
    6365Note that the filenames are swapped on the "right" node.  All you should need to change is what is after "data/" and before ".cinit" or ".crecv".  You are now ready to run the tmix experiment. 
    6466
    65 3.  Tmix relies upon a pre-determined start time to synchronize tmix on the two nodes.  On both nodes run the following command to determine the time and date:
     674.  Tmix relies upon a pre-determined start time to synchronize tmix on the two nodes.  On both nodes run the following command to determine the time and date:
    6668{{{
    6769date
     
    7072Decide on a start time about a minute or two in the future, relative to the time displayed by the date command.  It should be far enough in the future for you to issue the following command on both nodes and allow tmix to initialize.
    7173
    72 4.  Finally, execute the following command on both nodes:
     745.  Finally, execute the following command on both nodes:
    7375{{{
    7476tmix -s HH:MM:SS tmix.conf
     
    7678where HH:MM:SS is the chosen start time in hours minutes and seconds. 
    7779
    78 5.  Tmix on both hosts will load the data files and then wait until the designated start time. 
     806.  Tmix on both hosts will load the data files and then wait until the designated start time. 
    7981You will see "Running for 720 seconds" once tmix is ready to go.  When the start time arrives, Tmix will start running for 12 minutes (a 10 minute experiment plus 2 minutes of buffer).  You will not see any indication on the terminal that it has started running. 
    8082
    81 6.  One way to verify that tmix is running is to open another SSH terminal to either node and type:
     837.  One way to verify that tmix is running is to open another SSH terminal to either node and type:
    8284{{{
    8385top
     
    8587This shows a listing of the most active processes.  You should see tmix at the top of the list once it starts.  Top can also give you an indication of what percentage of the CPU tmix is using ( in the %CPU column).  If you see numbers near 80% or 90% you are near the capacity of the number of connections that this pair of nodes can simulate.  To exit top type 'q'.
    8688
    87 7.  Once the experiment is complete, a list of statistics will be output to the console.  Also, a set of log files with extentions .ert, .trt, .unc, .rt, and .ts will be created in the directory.  While tmix runs it is customary to experience a few errors, where connections fail to open or close.  It is also customary to see several errors at the end of the experiment indicating that some connections failed to close.  If, however, you see a steady stream of errors, something is wrong or you are trying to simulate too much traffic.  Type "Ctrl-c" on both terminals, and verify your tmix.conf file, and ensure you followed the above directions. 
     898.  Once the experiment is complete, a list of statistics will be output to the console.  Also, a set of log files with extentions .ert, .trt, .unc, .rt, and .ts will be created in the directory.  While tmix runs it is customary to experience a few errors, where connections fail to open or close.  It is also customary to see several errors at the end of the experiment indicating that some connections failed to close.  If, however, you see a steady stream of errors, something is wrong or you are trying to simulate too much traffic.  Type "Ctrl-c" on both terminals, and verify your tmix.conf file, and ensure you followed the above directions. 
    8890
    89 8.  To determine the number of bytes transferred during your experiment type the following on the '''"right"''' SSH terminal:
     919.  To determine the number of bytes transferred during your experiment type the following on the '''"right"''' SSH terminal:
    9092{{{
    9193bytesTxfrd tmixTutorial.rt
     
    9395Plotting this number in relation to the number of connection vectors for several experiments using different portions of traffic will allow us to determine at what point we can no longer reliably emulate traffic with a single pair of nodes.  Running this command on the "left" node will give us the number of bytes in the opposite direction.  This is not what we want to plot, however, because the bytes transferred in the opposite direction were less for the monitored link, and therefore are not the "weakest link", and will not be impacted as much when resources are saturated. 
    9496
    95 9.  To return to your home directory type:
     9710.  To return to your home directory type:
    9698{{{
    9799cd ..
     
    99101
    100102== D Iterate ==
    101 [[Image(calibration.png, 550, nolink, right)]] '''Repeat steps 1 through 9 of section C''' for various input files (i.e. 1of02.cinit.tcvec), and plot the resulting bytes transferred.  You should reach a point where the linear growth stops.  You can use the following table to record your results.     
     103[[Image(calibration.png, 550, nolink, right)]] '''Repeat steps 1 through 10 of section C''' for various input files (i.e. 1of02.cinit.tcvec), and plot the resulting bytes transferred.  You should reach a point where the linear growth stops.  You can use the following table to record your results.     
    102104
    103105