Changes between Version 11 and Version 12 of ClientSim


Ignore:
Timestamp:
Apr 27, 2010, 1:30:26 PM (14 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ClientSim

    v11 v12  
    11= BOINC client simulator =
    22
    3 The BOINC client simulator simulates a single BOINC client interacting with one or more projects.  The simulator models the CPU scheduling and work-fetch policies of the BOINC client very closely - in fact it uses the same source code as the core client for these policies.  The simulator implements several different scheduling policies: the ones currently in use, the ones used in the old (version 4) client, and several experimental policies that are under development.
     3The BOINC client simulator simulates a single BOINC client interacting with one or more projects.
     4The simulator models the CPU scheduling and work-fetch policies of the BOINC client very closely;
     5in fact it uses the same source code as the core client for these policies.
     6The simulator implements several different scheduling policies: the ones currently in use,
     7the ones used in the old (version 4) client,
     8and several experimental policies that are under development.
    49
    510The intended uses of the simulator include:
    … …  
    3641                <stdev>1e5</stdev>
    3742            </fpops>
    38             <working_set>100000000</working_set>
     43            <working_set>1e8</working_set>
     44            [<avg_ncpus>x</avg_ncpus>]
     45            [<natis>x</natis]
     46            [<ncudas>x</ncudas>]
     47            [<gpu_ram>x</gpu_ram>]
     48            [<flops_est>x</flops_est>]
    3949        </app>
    40         ...
     50        ... other apps
    4151        <available>
    4252            <frac>.7</frac>
    … …  
    4555        [<max_infeasible_count>N</max_infeasible_count>]
    4656    </project>
    47     ...
     57    ... other projects
    4858</projects>
    4959}}}
    5060
    51 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.
     61A project has one or more applications.
     62Each application has a given latency bound and working-set size.
     63The number of FP ops is a truncated normal distribution with the given mean and standard deviation.
    5264
    53 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.
     65The availability of the projects (i.e. the periods when scheduler RPCs succeed) is modeled with two parameters:
     66the duration of available periods are exponentially distributed with the given mean,
     67and the unavailable periods are exponentially distributed achieving the given available fraction.
    5468
    5569max_infeasible_count specifies how many jobs that are infeasible (due to deadline/workload)
    … …  
    6579    <m_nbytes>x</m_nbytes>
    6680    <p_ncpus>x</p_ncpus>
     81    [ <coproc>
     82        <type>cuda</type>
     83        <count>n</count>
     84        <available_ram>x</available_ram>
     85    </coproc> ]
    6786    <available>
    6887        <frac>.7</frac>
    … …  
    7695}}}
    7796
    78 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.
     97The available periods (i.e., when BOINC is running) and the idle periods
     98(i.e. when there is no user input) are modeled as above.
    7999
    80100=== sim_prefs.xml === #input_sim_prefs
    … …  
    105125  Use formula for DCF based on completion time mean/stdev.
    106126 --dirs d1 ...::
    107  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.
     127 chdir into each of the given directories, and runs a simulation based on the input files there.
     128 Prints summaries of each one separately, and a total summary.
    108129
    109130== Output files == #output
    … …  
    111132The simulator creates two output files:
    112133
    113 '''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].
     134'''sim_log.txt''': This is the message log (same as would be generated by the client).
     135Its contents are controlled by [#input_cc_config cc_config.xml].
    114136
    115137'''sim_out.html''': When viewed in a web browser, a 'time line' showing what's running when.