Changes between Version 9 and Version 10 of JobIn
- Timestamp:
- Jun 30, 2008, 12:58:58 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
JobIn
v9 v10 1 = Workunits =1 = Jobs = 2 2 3 A '''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.3 A BOINC job has two parts: 4 4 5 A workunit has several attributes. These are specified when the workunit is created; they are mandatory except where noted. 5 * A '''workunit''' describing the computation to be performed. 6 * One or more '''results''', each of which describes an instance of a computation, either unstarted, in progress, or completed. The BOINC client software refers to results as "tasks". 6 7 7 == Miscellaneous attributes == #misc 8 These entities are stored in the 'workunit' and 'result' database tables respectively. 9 10 BOINC provides a [WorkGeneration utility program and C function] for creating jobs. 11 12 == Workunit attributes == 13 14 A workunit has several attributes. 15 These are specified when the workunit is created; they are mandatory except where noted. 16 8 17 '''name''':: 9 18 A text string, unique across all workunits in the project. … … 12 21 '''input files''':: 13 22 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. 14 '''priority'''::15 (optional) Higher-priority work is dispatched first16 23 '''batch''':: 17 24 (optional) An integer; can be used to operate (cancel, change priority etc.) on groups of workunits. 18 25 19 == Resource estimates and bounds== #resources26 === Resource estimates and bounds === #resources 20 27 21 28 '''rsc_fpops_est''':: … … 32 39 It's important that you supply accurate values for these parameters. To get initial estimates, run your application on your own machines, and monitor the memory and disk usage. To 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]). 33 40 34 == Redundancy and scheduling attributes== #scheduling41 === Redundancy and scheduling attributes === #scheduling 35 42 36 43 '''delay_bound''':: … … 46 53 '''max_success_results''':: 47 54 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. 55 '''priority''':: 56 (optional) Higher-priority work is dispatched first 48 57 49 58 A workunit can experience any of several error conditions: … … 58 67 Too many total results have been sent for this workunit. 59 68 60 If any of these conditions holds, BOINC 'gives up' on the workunit and doesn't dispatch more results forit.69 If any of these conditions holds, BOINC doesn't dispatch more instances of the workunit. 61 70 71 == Result attributes == 72 73 The main attribute of a result is list of the names of the output files, 74 and the names by which the application refers to them. 75 76 A result has a '''server_state''' whose values include: 77 78 || ||Inactive (not ready to dispatch)|| 79 || ||Unsent (ready to send to a client, but not sent)|| 80 || ||In progress (sent, not done)|| 81 || ||Done successfully|| 82 || ||Timed out|| 83 || ||Done with error|| 84 || ||Not needed (work unit was finalized before this result was sent) || 85 86 Additional attributes are defined after the result is completed: 87 88 ||'''host''' ||The host that executed the computation.|| 89 ||'''exit status'''||The exit status (0 if success).|| 90 ||'''CPU time '''||The CPU time that was used.|| 91 ||'''output file info '''||The sizes and checksums of its output files.|| 92 ||'''stderr'''||The stderr output of the computation.|| 93 ||'''received time '''||The time when the result was received.||
