Changes between Version 3 and Version 4 of NonCpuIntensive

Timestamp:

Aug 24, 2012, 9:36:19 PM (12 years ago)

Author:

davea

Comment:

--

NonCpuIntensive

@@ -1 +1 @@
 = Non-CPU-intensive applications =
 
-A 'non-CPU-intensive' project is one whose applications use little CPU time. Examples include:
+A 'non-CPU-intensive' application is one that uses little CPU time.
+Examples include:
 
  * Host measurements
@@ -8 +9 @@
  * Network data access
 
-A non-CPU-intensive project is treated specially by the core client:
+Non-CPU-intensive applications can use chunks CPU time, as long as they do so infrequently.
 
- * The core client maintains one result for the project
- * The core client executes this result whenever computation is enabled, bypassing the normal CPU scheduling mechanism.
+A non-CPU-intensive application is treated specially by the client:
 
-A project labels itself as non-CPU-intensive by including the `<non_cpu_intensive>` flag in its [ProjectConfigFile configuration file].
+ * The client maintains exactly one task for the application.
+ * The client executes this task whenever computation is enabled, bypassing the normal CPU scheduling mechanism.
 
-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.
+Applications can be labeled as non-CPU-intensive in two ways:
 
-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.
+ * If the `<non_cpu_intensive>` flag is set in the project's [ProjectConfigFile configuration file],
+  then all applications are non-CPU-intensive.
+ * Individual applications can be marked as non-CPU-intensive
+  in their [XaddTool when they are created using xadd],
+  or using the [HtmlOps admin web interface].
+
+
+
+
+