Changes between Version 4 and Version 5 of JobIn


Ignore:
Timestamp:
May 18, 2007, 4:03:22 PM (17 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • JobIn

    v4 v5  
    44A '''workunit''' describes a computation to be performed. It is represented by a row in the 'workunit' database table. BOINC provides a [WorkGeneration utility program and C function] for creating workunits.
    55
    6 A workunit has several attributes that are specified when the workunit is created:
     6A workunit has several attributes.
     7These are specified when the workunit is created; they are mandatory except where noted.
    78
    89== Miscellaneous attributes ==
    910||'''name'''||  A text string, unique across all workunits in the project.||
    10 ||'''application''' ||  Which [CompoundApps 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.||
     11||'''application''' ||  Which [CompoundApps 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 either a) release new versions for all supported platforms, or b) create a new application. Such incompatibilities can often be avoided by using XML data format.||
    1112||'''input files '''    ||A list of the input files: their names, and the names by which the application refers to them. Typically these file are downloaded from a data server. However, if the <generate_locally/> element is present, the file is generated on the client (typically by an earlier instance of the same application). Applications should use file locking to prevent two jobs from generating the file at the same time.||
    12 ||'''priority'''        ||Higher-priority work is dispatched first||
    13 ||'''batch'''   ||An integer; can be used to operate (cancel, change priority etc.) on groups of workunits.||
     13||'''priority'''        ||(optional) Higher-priority work is dispatched first||
     14||'''batch'''   ||(optional) An integer; can be used to operate (cancel, change priority etc.) on groups of workunits.||
    1415
    1516== Resource estimates and bounds ==
     
    1920||'''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.||
    2021||'''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.||
     22
     23It's important that you supply accurate values for these parameters.
     24To get initial estimates, run your application on your own machines,
     25and monitor the memory and disk usage.
     26To view the distribution of FLOPs, use the script html/ops/job_times.php (the '''FLOP count statistics''' link on your project's [HtmlOps administrative web interface].
    2127
    2228== Redundancy and scheduling attributes ==