Changes between Version 1 and Version 2 of ClientSim
- Timestamp:
- Apr 25, 2007, 12:53:18 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ClientSim
v1 v2 1 1 = BOINC client simulator = 2 2 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. The simulator can be built with 'makefile_sim' on Unix or the 'sim' project on Windows. 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. The simulator can be built with 'makefile_sim' on Unix or the 'sim' project on Windows. 4 4 5 == Usage == 5 6 … … 7 8 sim [--duration X] [--delta X] [--dirs d1 ...] 8 9 }}} 9 runs the simulator with the given duration and time step. When run with --dirs, chdirs 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.10 10 11 runs the simulator with the given duration and time step. 12 13 When run with --dirs, chdirs 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. 11 14 12 15 == Output files == 13 The simulator creates two output files: '''sim_log.txt''': This is the message log (same as would be generated by the client). Its contents are controlled by cc_config.xml. '''sim_out.html''': When viewed in a web browser, a 'time line' showing what's running when.14 16 17 The simulator creates two output files: 18 19 '''sim_log.txt''': This is the message log (same as would be generated by the client). Its contents are controlled by cc_config.xml. 20 21 '''sim_out.html''': When viewed in a web browser, a 'time line' showing what's running when. 15 22 16 23 == Input files == 17 The input consists of four files. 24 25 The input consists of four files. 26 18 27 === sim_projects.xml === 19 This describes a set of attached projects. 28 29 This describes a set of attached projects. 30 20 31 {{{ 21 32 <projects> … … 41 52 </projects> 42 53 }}} 43 A project has one or more applications. Each application has a given latency bound and working-set size. The number of FP ops is a truncated normal distribution with the given mean and standard deviation. The availability of the projects (i.e. the periods when scheduler RPCs succeed) is modeled with two parameters: the duration of available periods are exponentially distributed with the given mean, and the unavailable periods are exponentially distributed achieving the given available fraction.44 54 55 A project has one or more applications. Each application has a given latency bound and working-set size. The number of FP ops is a truncated normal distribution with the given mean and standard deviation. 56 57 The availability of the projects (i.e. the periods when scheduler RPCs succeed) is modeled with two parameters: the duration of available periods are exponentially distributed with the given mean, and the unavailable periods are exponentially distributed achieving the given available fraction. 45 58 46 59 === sim_host.xml === 47 This describes the host hardware and availability. 60 61 This describes the host hardware and availability. 62 48 63 {{{ 49 64 <host> … … 61 76 </host> 62 77 }}} 63 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. 78 79 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. 80 64 81 === sim_prefs.xml === 65 Same format as the global_prefs.xml file. 82 83 Same format as the global_prefs.xml file. 84 66 85 === cc_config.xml === 67 Same format as the client's cc_config.xml file. 86 87 Same format as the client's cc_config.xml file.
