Workunits

A workunit describes a computation to be performed. Workunits are maintained in the workunit table in the BOINC DB. The attributes of a workunit include:

• Its name (unique across all workunits in the project).
• Its application.
• An XML document describing its input files and other parameters (see below).
• The estimated resource requirements of the work unit (computation, memory, disk space).
• A delay bound: upper bound on how long an instance of this work unit should take to complete. This limits what hosts the workunit is sent to, and it's used to assign result deadlines and times for retrying results.

The inputs to a workunit are described by an XML document of the form

[ <file_info>...</file_info> ]
[ ... ]
<workunit>
    <app_name>blah</app_name>
    [ <command_line>-flags xyz</command_line> ]
    [ <env_vars>name=val&name=val</env_vars> ]
    [ <file_ref>...</file_ref> ]
    [ ... ]
<workunit>

• The <command_line> element, if present, is the command-line arguments to be passed to the main program.
• The <env_vars> element, if present, is a list of environment variables to be passed to the main program.
• Each <file_ref> element describes a reference to an input file, each of which is described by a <file_info> element.

A workunit is associated with an application, not with a particular version or range of versions. If the format of your input data 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.

The create_work utility program provides a simplified interface for creating workunits.