Changes between Version 1 and Version 2 of NonCpuIntensive
- Timestamp:
- Apr 25, 2007, 10:05:21 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NonCpuIntensive
v1 v2 1 1 = Non-CPU-intensive applications = 2 2 3 A 'non-CPU-intensive' project is one whose applications use little CPU time. Examples include: 3 A 'non-CPU-intensive' project is one whose applications use little CPU time. Examples include: 4 4 5 * Host measurements 5 6 * Network measurements … … 7 8 * Network data access 8 9 9 A non-CPU-intensive project is treated specially by the core client: 10 A non-CPU-intensive project is treated specially by the core client: 11 10 12 * The core client maintains one result for the project 11 13 * The core client executes this result whenever computation is enabled, bypassing the normal CPU scheduling mechanism. 12 14 13 A project labels itself as non-CPU-intensive by including the <non_cpu_intensive> flag in its [http://boinc.berkeley.edu/configuration.phpconfiguration file]15 A project labels itself as non-CPU-intensive by including the `<non_cpu_intensive>` flag in its [ProjectConfigFile configuration file] 14 16 15 17 This attribute is at the project level; there is no provision for a project to have some applications that are CPU intensive and some that aren't. 16 18 17 19 Non-CPU-intensive applications can use chunks CPU time; this won't break anything, and the CPU scheduler will adjust to it by changing its estimates of 'CPU efficiency'. However, non-CPU-intensive applications should try not to use more CPU time than their resource share fraction indicates. 18