Changes between Version 4 and Version 5 of BackendPrograms
- Timestamp:
- Oct 10, 2007, 8:21:34 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BackendPrograms
v4 v5 14 14 How long to sleep when there's nothing to do. 15 15 16 == Work generator == 16 == Work generator == #workgen 17 17 18 18 There is one work generator per application. It creates workunits and the corresponding input files. It is application-specific, and uses [WorkGeneration BOINC library functions] for registering the workunits in the database. … … 20 20 During testing, you can create a single workunit using [WorkGeneration create_work], then use the daemon program [WorkGeneration#make_work make_work] to copy this workunit as needed to maintain a given supply of work. 21 21 22 == Feeder == 22 == Feeder == #feeder 23 23 24 24 This program is supplied by BOINC and is application independent. It creates a shared-memory segment used to pass database records to CGI scheduler processes. This data includes applications, application versions, and 'work items' (an unsent result and its corresponding workunit). It has the following command-line options: … … 39 39 If a user's project preferences include elements of the form `<app_id>N</app_id>` then the scheduler will send the user work only from those applications. 40 40 41 == Transitioner == 41 == Transitioner == #transitioner 42 42 43 43 This program is supplied by BOINC and is application independent. It handles state transitions of workunits and results. It generates initial results for workunits, and generates more results when timeouts or errors occur. 44 44 45 == Validator == 45 == Validator == #validator 46 46 47 47 There is one validator per application. It compares redundant results and selects a canonical result representing the correct output, and a canonical credit granted to users and hosts that return the correct output. Depending on your application, you may be able to use a BOINC-supplied validator, or you may have to [ValidationIntro develop a customized validator]. 48 48 49 == Assimilator == 49 == Assimilator == #assimilator 50 50 51 51 There is one assimilator per application. It handles workunits that are 'completed': that is, that have a canonical result or for which an error condition has occurred. Handling a successfully completed result might involve record results in a database and perhaps generating more work. See [AssimilateIntro more details]. 52 52 53 == File deletion == 53 == File deletion == #file_deleter 54 54 55 55 The application-independent program [FileDeleter file_deleter] deletes input and output files when they are no longer needed. 56 56 57 == Database purging == 57 == Database purging == #db_purge 58 58 59 59 The application-independent program [DbPurge db_purge] removes work-related database entries when they are no longer needed. This keeps your database at a constant size even when your project runs for a long time.
