svn commit: r1544183 - /uima/site/trunk/uima-website/xdocs/doc-uimaducc-whatitam.xml

[ea...@apache.org]

Author: eae
Date: Thu Nov 21 13:58:00 2013
New Revision: 1544183

URL: http://svn.apache.org/r1544183
Log:
UIMA-3407 minor updates

Modified:
    uima/site/trunk/uima-website/xdocs/doc-uimaducc-whatitam.xml

Modified: uima/site/trunk/uima-website/xdocs/doc-uimaducc-whatitam.xml
URL: http://svn.apache.org/viewvc/uima/site/trunk/uima-website/xdocs/doc-uimaducc-whatitam.xml?rev=1544183&r1=1544182&r2=1544183&view=diff
==============================================================================
--- uima/site/trunk/uima-website/xdocs/doc-uimaducc-whatitam.xml (original)
+++ uima/site/trunk/uima-website/xdocs/doc-uimaducc-whatitam.xml Thu Nov 21 13:58:00 2013
@@ -56,7 +56,7 @@ in a pipeline.
 DUCC's resource manager uses the combination of specified memory requirement and
 process class to find space to run each new managed process instance. 
 The resource manager does not overcommit RAM memory for machines, and DUCC uses Linux 
-cgroups to constrain managed processes from interfering with each other.
+cgroups to constrain all managed processes from interfering with each other.
 Only processes that exceed their requested memory allocation will be subject to paging.
 The resource manager employs process preemption to dynamically rebalance compute
 resources between collection processing jobs.
@@ -67,7 +67,7 @@ multiple users need to efficiently share
 computational activities. All processes run with
 the credentials of the submitting user. Process logfiles and DUCC collected performance
 data are stored in user filesystem space. This allows/forces each
-user to decide how to manage the metadata associated work submitted to DUCC.
+user to decide how to manage the metadata associated with work submitted to DUCC.
    </p>
    <p>
 The following sections will describe each of the three types of DUCC managed processes
@@ -114,6 +114,9 @@ During the job DUCC will automatically s
 number of number of work items left to do, the number of threads per Job Process, and the 
 amount of resources available to the job.
    </p>
+   <p>
+Jobs are tracked on the Jobs page of DUCC webserver.
+   </p>
   </subsection>
 
    <subsection name="DUCC Services">
@@ -121,7 +124,7 @@ amount of resources available to the job
 A DUCC service is a process whose life cycle DUCC will manage and/or whose health DUCC will monitor.
 The service can be configured to 
 be automatically started as soon as resources are available, or it can be started on demand, when DUCC is
-asked to start a job or another service that have declared a dependency on it. 
+asked to start a job or another service that has declared a dependency on it. 
 Another configuration parameter specifies the default number of service processes to start.
 Users can also start or stop services manually, as well as manually change the number of running instances.
    </p> 
@@ -142,8 +145,7 @@ Services are tracked on the Services pag
    <subsection name="DUCC Arbitrary Processes">
    <p>
 DUCC can be used to run an arbitrary process on a DUCC worker node. 
-Resources are allocated according to the memory size and scheduling class requested,
-and the process is run in a cgroup.
+Resources are allocated according to the memory size and scheduling class requested.
 The allocated resource is freed when the process terminates.
    </p> 
    <p>
@@ -164,34 +166,44 @@ DUCC offers a number of potential advant
 	<dt>Threading</dt>
 	<dd>
 Hadoop mapper processes are intended to have a single analytic thread.
-DUCC is designed to run multiple UIMA pipelines in 
-a single job process,
-allowing sharing of static Java objects and yielding significant RAM saving.
+DUCC is designed to run multiple UIMA pipelines in a single job process,
+allowing sharing of static Java objects.
+	</dd> <br></br>
+
+	<dt>Guaranteed RAM</dt>
+	<dd>
+DUCC's allocation model and use of cgroups guarantee every managed process the amount
+of real RAM memory requested.
 	</dd> <br></br>
+
 	<dt>Application Interface</dt>
 	<dd>
 The application interfaces for a UIMA application continue to be UIMA-standard
 components: CollectionReader, CasConsumer, and CasMultiplier.
 Hadoop requires integrating a new set of interface components.
 	</dd> <br></br>
+
 	<dt>Collection Processing Errors</dt>
 	<dd>
-If a mapper fails to handle a single work item in a collection the entire
-collection must be reprocessed after fixing the mapper problem, no
+If a Hadoop mapper fails to handle any work item in a collection the entire
+collection must be reprocessed after fixing the mapper problem; there is no
 way to make incremental progress.
 DUCC Jobs are designed to preserve previous results, if appropriate.
 	</dd> <br></br>
-	<dt>Performance Reports</dt>
+
+	<dt>Performance Analysis</dt>
 	<dd>
 For every job DUCC automatically provides the performance breakdown for every
 UIMA component.
 	</dd> <br></br>
+
 	<dt>Other Workloads</dt>
 	<dd>
 DUCC has support for managing a wide range of processes, including non-UIMA
 processes. For example, DUCC could dynamically start a Hadoop instance
 on a subset of DUCC worker machines.
 	</dd> <br></br>
+
 	<dt>Debug Support</dt>
 	<dd>
 DUCC offers tight integration with Eclipse debugging.