Changes between Version 5 and Version 6 of ClientSim
- Timestamp:
- Jul 17, 2007, 1:21:28 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ClientSim
v5 v6 2 2 3 3 The 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. 6 6 7 7 == Input files == … … 9 9 The input consists of four files. 10 10 11 === sim_projects.xml === 11 === sim_projects.xml === #input_sim_projects 12 12 13 13 This describes a set of attached projects. … … 45 45 to tolerate over before giving up in work-send loop. Default is 0. 46 46 47 === sim_host.xml === 47 === sim_host.xml === #input_sim_host 48 48 49 49 This describes the host hardware and availability. … … 67 67 The available periods (i.e., when BOINC is running) and the idle periods (i.e. when there is no user input) are modeled as above. 68 68 69 === sim_prefs.xml === 69 === sim_prefs.xml === #input_sim_prefs 70 70 71 71 Same format as the global_prefs.xml file. 72 72 73 === cc_config.xml === 73 === cc_config.xml === #input_cc_config 74 74 75 Same format as the client's cc_config.xmlfile.75 Same format as the [ClientMessages client's cc_config.xml] file. 76 76 77 == Building and running the simulator == 77 == Building and running the simulator == #build_and_run 78 78 The simulator can be built with 'makefile_sim' on Unix or the 'sim' project on Windows. 79 79 The usage is: … … 96 96 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. 97 97 98 == Output files == 98 == Output files == #output 99 99 100 100 The simulator creates two output files: 101 101 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]. 103 103 104 104 '''sim_out.html''': When viewed in a web browser, a 'time line' showing what's running when.