Changes between Version 1 and Version 2 of JobIn


Ignore:
Timestamp:
Apr 20, 2007, 5:01:46 PM (17 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JobIn

    v1 v2  
    66A workunit has several attributes that are specified when the workunit is created:
    77
     8== Miscellaneous attributes ==
    89||'''name'''||  A text string, unique across all workunits in the project.||
    910||'''application''' ||  Which [http://boinc.berkeley.edu/app.php application] will perform the computation. A workunit is associated with an application, not with a particular version or range of versions. If the input data format changes in a way that is incompatible with older versions, you must create a new application. This can often be avoided by using XML data format.||
     
    1112||'''priority'''        ||Higher-priority work is dispatched first||
    1213||'''batch'''   ||An integer; can be used to operate (cancel, change priority etc.) on groups of workunits.||
    13 [[BR]]
    14 {{{
    15 #!html
    16 <h2 style="text-align: center">Resource estimates and bounds</h2>
    17 }}}
    18 [[BR]]
     14
     15== Resource estimates and bounds ==
     16
    1917||'''rsc_fpops_est'''||         An estimate of the average number of floating-point operations required to complete the computation. This used to estimate how long the computation will take on a given host.||
    2018||'''rsc_fpops_bound''' ||      A bound on the number of floating-point operations required to complete the computation. If this bound is exceeded, the application will be aborted.||
    2119||'''rsc_memory_bound '''       ||An estimate of application's largest working set size. The workunit will only be sent to hosts with at least this much available RAM.||
    2220||'''rsc_disk_bound     '''||A bound on the maximum disk space used by the application, including all input, temporary, and output files. The workunit will only be sent to hosts with at least this much available disk space. If this bound is exceeded, the application will be aborted.||
    23 [[BR]]
    24 {{{
    25 #!html
    26 <h2 style="text-align: center">Redundancy and scheduling attributes</h2>
    27 }}}
    28 [[BR]]
     21
     22== Redundancy and scheduling attributes ==
     23
    2924||'''delay_bound''' ||  An upper bound on the time (in seconds) between sending a result to a client and receiving a reply. The scheduler won't issue a result if the estimated completion time exceeds this. If the client doesn't respond within this interval, the server 'gives up' on the result and generates a new result, to be assigned to another client.   Set this to several times the average execution time of a workunit on a typical PC. If you set it too low, BOINC may not be able to send some results, and the corresponding workunit will be flagged with an error. If you set it too high, there may a corresponding delay in getting results back.||
    3025||'''min_quorum '''     ||The minimum size of a 'quorum'. The validator is run when there are this many successful results. If a strict majority agree, they are considered correct. Set this to two or more if you want redundant computing.||
     
    3429||'''max_success_results '''    ||If the number of success results for this workunit exceeds this, and a consensus has not been reached, the workunit is declared to be in error. This safeguards against workunits that produce nondeterministic results.||
    3530
    36 A workunit has a dynamic attribute:
     31A workunit can experience any of several error conditions:
    3732
    38 ||'''error mask'''||    A bit mask of various error conditions: ||
    39 || ||  ''' WU_ERROR_COULDNT_SEND_RESULT:''' The BOINC scheduler was unable to send the workunit to a large number (~100) of hosts, probably because its resource requirements (disk, memory, CPU) were too large for the hosts, or because no application version was available for the hosts' platforms. In this case BOINC 'gives up' on the workunit.||
    40 ||  || ''' WU_ERROR_TOO_MANY_ERROR_RESULTS:''' Too many results with error conditions (upload/download problem, client crashes) have been returned for this work unit.||
    41 ||  ||  ''' WU_ERROR_TOO_MANY_SUCCESS_RESULTS:''' Too many successful results have been returned without consensus. This indicates that the application may be nondeterministic.||
    42 || ||  '''WU_ERROR_TOO_MANY_TOTAL_RESULTS:''' Too many total results have been sent for this workunit. ||
     33|| ||  ''' WU_ERROR_COULDNT_SEND_RESULT''' || The BOINC scheduler was unable to send the workunit to a large number (~100) of hosts, probably because its resource requirements (disk, memory, CPU) were too large for the hosts, or because no application version was available for the hosts' platforms. In this case BOINC 'gives up' on the workunit.||
     34||  || ''' WU_ERROR_TOO_MANY_ERROR_RESULTS''' || Too many results with error conditions (upload/download problem, client crashes) have been returned for this work unit.||
     35||  ||  ''' WU_ERROR_TOO_MANY_SUCCESS_RESULTS''' || Too many successful results have been returned without consensus. This indicates that the application may be nondeterministic.||
     36|| ||  '''WU_ERROR_TOO_MANY_TOTAL_RESULTS''' || Too many total results have been sent for this workunit. ||
    4337
    4438If any of these conditions holds, BOINC 'gives up' on the workunit and doesn't dispatch more results for it.