Changes between Version 12 and Version 13 of GeniTmixCalibTutorial


Ignore:
Timestamp:
06/19/14 15:35:09 (5 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTmixCalibTutorial

    v12 v13  
    4343
    4444== C Run Tmix  Script and view data files ==
     451. Make a new directory for this experiment, change to it, and copy tmix.conf there by typing:
     46{{{
     47mkdir 1of10
     48cd 1of10
     49cp ../tmix.conf .
     50}}}
    4551
    46 1.  '''Edit your tmix.conf''' file using a terminal text editor such that your Crecv and Cinit lines are the following. 
     522.  '''Edit the tmix.conf''' file using a terminal text editor such that your Crecv and Cinit lines are the following. 
    4753{{{
    4854Cinit_Trace = /opt/tmix-1.2/data/1of10.cinit.tcvec
     
    5763Note 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. 
    5864
    59 2.  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:
     653.  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:
    6066{{{
    6167date
     
    6470Decide 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.
    6571
    66 3.  Finally, execute the following command on both nodes:
     724.  Finally, execute the following command on both nodes:
    6773{{{
    6874tmix -s HH:MM:SS tmix.conf
     
    7076where HH:MM:SS is the chosen start time in hours minutes and seconds. 
    7177
    72 4.  Tmix on both hosts will load the data files and then wait until the designated start time. 
    73 You will see "Running for ???? seconds" once tmix is ready to go.  When the start time hits, Tmix will start running for 12 minutes (a 10 minute experiment plus 2 minutes of buffer).  Once The experiment has completed you will see output indicating the the log files have been output.  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.  Type "Ctrl-c", and verify your tmix.conf file, and ensure you followed the directions above
     785.  Tmix on both hosts will load the data files and then wait until the designated start time. 
     79You will see "Running for ???? 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
    7480
    75 5.  One way to verify that tmix is running is to open another SSH terminal to either node and type:
     816.  One way to verify that tmix is running is to open another SSH terminal to either node and type:
    7682{{{
    7783top
    7884}}}
    79 This 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.  If you see numbers near 80 or 90% you are near the cap.    To exit top type 'q'.
     85This 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'.
    8086
    81 After about 12 minutes, the experiment will complete, and 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
     877.  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
    8288
    83 == D Delete Resources ==
     898.  To determine the number of bytes transferred during your experiment type:
     90{{{
     91bytesTxfrd tmixTutorial.rt
     92}}}
     93Plotting 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.   
     94
     959.  To return to your home directory type:
     96{{{
     97cd ..
     98}}}
     99
     100== D Iterate ==
     101Repeat 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.     
     102
     103== E Delete Resources ==
    84104Once your experiment is complete and you have collected your results, you should return the reserved resources.  To do so, follow the step below which matches your choice to use GENI Portal or Omni.
    85 === D.1 Using GENI Portal ===
     105=== E.1 Using GENI Portal ===
    861061.  '''Click on slices''' in the upper right-hand corner. 
    87107
     
    901103.  Click "Delete Resources" again to confirm that you want to delete all reserved resources. 
    91111
    92 === D.2 Using Omni ===
     112=== E.2 Using Omni ===
    93113 In the terminal execute the following command:
    94114{{{