Changes between Version 5 and Version 6 of ClientSim


Ignore:
Timestamp:
Jul 17, 2007, 1:21:28 PM (17 years ago)
Author:
Nicolas
Comment:

Added shorter anchors, some links

Legend:

Unmodified
Added
Removed
Modified
  • ClientSim

    v5 v6  
    22
    33The BOINC client simulator simulates the CPU scheduling and work-fetch policies of the BOINC client. It uses the same source code as the core client for these policies. You can use the simulator in either of two ways:
    4  * Through a [http://boinc.berkeley.edu/sim_form.php web interface]. This lets you do one simulation at a time, and shows you results graphically.
    5  * Compile it your self. This provides a more flexible, but less convenient, interface.
     4 * Through a [/sim_form.php web interface]. This lets you do one simulation at a time, and shows you results graphically.
     5 * Compile it yourself. This provides a more flexible, but less convenient, interface.
    66
    77== Input files ==
     
    99The input consists of four files.
    1010
    11 === sim_projects.xml ===
     11=== sim_projects.xml === #input_sim_projects
    1212
    1313This describes a set of attached projects.
     
    4545to tolerate over before giving up in work-send loop.  Default is 0.
    4646
    47 === sim_host.xml ===
     47=== sim_host.xml === #input_sim_host
    4848
    4949This describes the host hardware and availability.
     
    6767The available periods (i.e., when BOINC is running) and the idle periods (i.e. when there is no user input) are modeled as above.
    6868
    69 === sim_prefs.xml ===
     69=== sim_prefs.xml === #input_sim_prefs
    7070
    7171Same format as the global_prefs.xml file.
    7272
    73 === cc_config.xml ===
     73=== cc_config.xml === #input_cc_config
    7474
    75 Same format as the client's cc_config.xml file.
     75Same format as the [ClientMessages client's cc_config.xml] file.
    7676
    77 == Building and running the simulator ==
     77== Building and running the simulator == #build_and_run
    7878The simulator can be built with 'makefile_sim' on Unix or the 'sim' project on Windows.
    7979The usage is:
     
    9696 chdir into each of the given directories, and runs a simulation based on the input files there. Prints summaries of each one separately, and a total summary.
    9797
    98 == Output files ==
     98== Output files == #output
    9999
    100100The simulator creates two output files:
    101101
    102 '''sim_log.txt''': This is the message log (same as would be generated by the client). Its contents are controlled by cc_config.xml.
     102'''sim_log.txt''': This is the message log (same as would be generated by the client). Its contents are controlled by [#input_cc_config cc_config.xml].
    103103
    104104'''sim_out.html''': When viewed in a web browser, a 'time line' showing what's running when.