Changes between Version 12 and Version 13 of GeniTmixCalibTutorial
- Timestamp:
- 06/19/14 15:35:09 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeniTmixCalibTutorial
v12 v13 43 43 44 44 == C Run Tmix Script and view data files == 45 1. Make a new directory for this experiment, change to it, and copy tmix.conf there by typing: 46 {{{ 47 mkdir 1of10 48 cd 1of10 49 cp ../tmix.conf . 50 }}} 45 51 46 1. '''Edit yourtmix.conf''' file using a terminal text editor such that your Crecv and Cinit lines are the following.52 2. '''Edit the tmix.conf''' file using a terminal text editor such that your Crecv and Cinit lines are the following. 47 53 {{{ 48 54 Cinit_Trace = /opt/tmix-1.2/data/1of10.cinit.tcvec … … 57 63 Note 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. 58 64 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: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: 60 66 {{{ 61 67 date … … 64 70 Decide 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. 65 71 66 3. Finally, execute the following command on both nodes:72 4. Finally, execute the following command on both nodes: 67 73 {{{ 68 74 tmix -s HH:MM:SS tmix.conf … … 70 76 where HH:MM:SS is the chosen start time in hours minutes and seconds. 71 77 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.78 5. Tmix on both hosts will load the data files and then wait until the designated start time. 79 You 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. 74 80 75 5. One way to verify that tmix is running is to open another SSH terminal to either node and type:81 6. One way to verify that tmix is running is to open another SSH terminal to either node and type: 76 82 {{{ 77 83 top 78 84 }}} 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'.85 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'. 80 86 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.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. 82 88 83 == D Delete Resources == 89 8. To determine the number of bytes transferred during your experiment type: 90 {{{ 91 bytesTxfrd tmixTutorial.rt 92 }}} 93 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. 94 95 9. To return to your home directory type: 96 {{{ 97 cd .. 98 }}} 99 100 == D Iterate == 101 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. 102 103 == E Delete Resources == 84 104 Once 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 === 86 106 1. '''Click on slices''' in the upper right-hand corner. 87 107 … … 90 110 3. Click "Delete Resources" again to confirm that you want to delete all reserved resources. 91 111 92 === D.2 Using Omni ===112 === E.2 Using Omni === 93 113 In the terminal execute the following command: 94 114 {{{
