Changes between Version 15 and Version 16 of ContainmentInSeattle

Changes between Version 15 and Version 16 of ContainmentInSeattle

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 15 and Version 16 of ContainmentInSeattle

Please note that these Trac pages are no longer being updated. Wiki contents/documentation have moved to GitHub.

Changes between Version 15 and Version 16 of ContainmentInSeattle

Show
Ignore:
Timestamp:
12/20/09 14:27:01 (10 years ago)
Author:
cosminb
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContainmentInSeattle

    v15 v16  
    3737Prior to this section, please complete the steps in the 'Building and Configuring' and 'Running the Seattle Node Directory Service' sections. 
    3838 
    39 <rest of section coming soon> 
     391) Run a command in the following format to start the experiment. 
     40{{{ 
     41python deploycncexperiment.py wan <number clients> <experiment run duration in seconds> <number of client groups> 
     42}}} 
     43 
     44The nummber of client groups argument basically indicates the nubmer of unique keys. The script will set up clients to have one userkey each. So for 2 client groups, half of the vessels will have one key, and the other half will share a completely different key.  
     45 
     46For example, the following command will run an experiment with 100 clients for 20 minutes, with all clients sharing the same single userkey. 
     47{{{ 
     48python deploycncexperiment.py wan 100 1200 1 
     49}}} 
     50 
     512) Wait for the experiment to complete. This may take a few hours if the number of clients is greater than 100 due to high costs of setting up the experiment and downloaging the log data. You can track the progress of the experiment in the log file generated by the script named 'cnc_experiment_out'. 
     52 
     533) Once the experiment is completed, there will be a subdirectory in testdir (on the machine the experiment script was run from) generated with a collection of logs from all the clients in the experiment. We will refer to this subdirectory as 'the result directory'. Stop all Seattle Node Directory Servers in your farm. From each machine in your farm, look inside the testdir directory and find the logfiles with the prefix 'cncserverlog'. Copy these files to the result directory. 
     54 
     554)On the machine the experiment script was run on, browse to the parent directory of testdir. Copy analyze_logs.py to this directory (analyze_logs.py is in the cnc code in the cncSystemPerformance directory). Then, making sure you are in the parent directory of test dir (not in testdir directory), run the following command to analyze your results. 
     56{{{ 
     57python analyze_logs.py  testdir [name of result dir] > temp.txt 
     58}}} 
     59In place of [name of result dir], make sure to enter the actual name of the result directory. 
     60This may take a fw minutes to run depending on the number and size of the logs.  
     61 
     62The report will be stored in the file temp.txt. 
     63 
    4064 
    4165 
     
    7195 
    7296deploycncexperiment.mix - support for automatically aquiring arbitrary numbers of vessels and running containment experiments. The recommeded way to use this script is to first manually configure and start the server, then use this script to aquire and start clients. 
     97 
     98analyze_logs.py - a result analysis script that will parse log files from the Seattle Node Directory service and from its clients to determine information such as cache accuracy, load on clients, and load on servers.