Changes between Version 74 and Version 75 of GeniTmixCalibTutorial


Ignore:
Timestamp:
06/21/14 18:08:48 (5 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTmixCalibTutorial

    v74 v75  
    7878where HH:MM:SS is the chosen start time in hours minutes and seconds. 
    7979
    80 6.  Tmix on both hosts will load the data files and then wait until the designated start time. 
     806.  On both hosts Tmix will load the data files and then wait until the designated start time. 
    8181You 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. 
    8282
     
    8585top
    8686}}}
    87 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 ( 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'.
     87This 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.  Type 'q' to exit top.
    8888
    89 8.  Once the experiment is complete, a list of statistics will be output to the console.  Also, a set of log files with extensions .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 extensions .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, verify your "tmix.conf" file, and ensure you followed the above directions. 
    9090
    91 9.  To determine the number of bytes transferred during your experiment type the following on the '''"right"''' SSH terminal:
    92 {{{
     919.  To determine the number of bytes transferred during your experiment, type the following on the '''"right"''' SSH terminal:
     92{{{,
    9393bytesTxfrd tmixTutorial.rt
    9494}}}
    95 Plotting 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
     95Plotting 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 fewer bytes are transferred in the opposite direction in the traffic we are replaying.  We are are instead interested in plotting data for the link which places the most demand on system resources
    9696
    97 10.  To return to your home directory type:
     9710.  To return to your home directory, type:
    9898{{{
    9999cd ..
     
    101101
    102102== E. Iterate ==
    103 [[Image(calibration.png, 550, nolink, right)]] '''Repeat steps 1 through 10 of section D''' 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.  The graph to the right is the resulting graph from calibrating two GENI nodes.  At least 3 pairs of nodes would be needed to reliably replay data on these nodes. You can use the following table to record your results.     
     103[[Image(calibration.png, 550, nolink, right)]] '''Repeat steps 1 through 10 of section D''' for various input files (i.e. 1of02.cinit.tcvec), and plot the resulting number of bytes transferred.  You should reach a point where the linear growth stops.  The graph to the right is the resulting graph from calibrating two GENI nodes.  The graph indicates that given the current environment, at least three pairs of this type of node would be required to reliably replay the traffic. You can use the following table to record the calibration results for your nodes.  Depending on the properties of the nodes you are using, the network traffic, and the resource utilization, your results will likely be different.        
    104104
    105105
     
    1251251.  In GENI portal, '''Click on slices''' in the upper right-hand corner. 
    126126
    127 2.  Find your slice in the list, and click on the corresponding '''Delete Resources''' button.
     1272.  Find your slice in the list and click on the corresponding '''Delete Resources''' button.
    128128
    129 3.  Click "Delete Resources" again to confirm that you want to delete all reserved resources. 
     1293.  Click '''"Delete Resources"''' again to confirm that you want to delete all reserved resources. 
    130130