| 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 | | |
| 5 | | == Usage == |
| 6 | | |
| 7 | | {{{ |
| 8 | | sim [--duration X] [--delta X] [--server_uses_workload] [--dirs d1 ...] |
| 9 | | }}} |
| 10 | | |
| 11 | | --duration:: |
| 12 | | simulate this much time. |
| 13 | | --delta:: |
| 14 | | time step of simulation. |
| 15 | | --server_uses_workload:: |
| 16 | | servers take existing workload into account when deciding whether to send jobs. |
| 17 | | --dcf_dont_use:: |
| 18 | | Duration correction factor (DCF) is one. |
| 19 | | --dcf_stats:: |
| 20 | | Use formula for DCF based on completion time mean/stdev. |
| 21 | | --dirs d1 ...:: |
| 22 | | 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. |
| 23 | | |
| 24 | | == Output files == |
| 25 | | |
| 26 | | The simulator creates two output files: |
| 27 | | |
| 28 | | '''sim_log.txt''': This is the message log (same as would be generated by the client). Its contents are controlled by cc_config.xml. |
| 29 | | |
| 30 | | '''sim_out.html''': When viewed in a web browser, a 'time line' showing what's running when. |
| | 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. |
| | 76 | |
| | 77 | == Building and running the simulator == |
| | 78 | The simulator can be built with 'makefile_sim' on Unix or the 'sim' project on Windows. |
| | 79 | The usage is: |
| | 80 | |
| | 81 | {{{ |
| | 82 | sim [--duration X] [--delta X] [--server_uses_workload] [--dirs d1 ...] |
| | 83 | }}} |
| | 84 | |
| | 85 | --duration:: |
| | 86 | simulate this much time. |
| | 87 | --delta:: |
| | 88 | time step of simulation. |
| | 89 | --server_uses_workload:: |
| | 90 | servers take existing workload into account when deciding whether to send jobs. |
| | 91 | --dcf_dont_use:: |
| | 92 | Duration correction factor (DCF) is one. |
| | 93 | --dcf_stats:: |
| | 94 | Use formula for DCF based on completion time mean/stdev. |
| | 95 | --dirs d1 ...:: |
| | 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 | |
| | 98 | == Output files == |
| | 99 | |
| | 100 | The simulator creates two output files: |
| | 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. |
| | 103 | |
| | 104 | '''sim_out.html''': When viewed in a web browser, a 'time line' showing what's running when. |
| | 105 | |
