You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@uima.apache.org by ea...@apache.org on 2008/08/04 03:57:39 UTC
svn commit: r682240 - in /incubator/uima/site/trunk/uima-website: docs/
docs/images/getting-started/ xdocs/
Author: eae
Date: Sun Aug 3 18:57:39 2008
New Revision: 682240
URL: http://svn.apache.org/viewvc?rev=682240&view=rev
Log:
UIMA-1134
Added:
incubator/uima/site/trunk/uima-website/docs/images/getting-started/multiplecrscaleout.png (with props)
incubator/uima/site/trunk/uima-website/docs/images/getting-started/singlecrscaleout.PNG (with props)
Modified:
incubator/uima/site/trunk/uima-website/docs/doc-uimaas-what.html
incubator/uima/site/trunk/uima-website/docs/images/getting-started/runremoteasyncae.png
incubator/uima/site/trunk/uima-website/xdocs/doc-uimaas-what.xml
Modified: incubator/uima/site/trunk/uima-website/docs/doc-uimaas-what.html
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/doc-uimaas-what.html?rev=682240&r1=682239&r2=682240&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/docs/doc-uimaas-what.html (original)
+++ incubator/uima/site/trunk/uima-website/docs/doc-uimaas-what.html Sun Aug 3 18:57:39 2008
@@ -270,13 +270,13 @@
<tr><td bgcolor="#9289A2">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="UIMA AS - Example Application Scenario"><strong>UIMA AS - Example Application Scenario</strong></a>
+ <a name="UIMA AS - Example Application Scenarios"><strong>UIMA AS - Example Application Scenarios</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
- One problem that has been raised on the UIMA mailing lists is how to "push" documents into a UIMA processing pipeline. The simple answer with UIMA AS is to implement the processing pipeline as a UIMA AS service, and push requests from a custom application. Multiple instances of the processing pipeline service could be instantiated to increase throughput. Note that the processing pipeline could itself contain a CAS Multiplier component so that a single request to the service could be a reference to collection of artifacts to be processed.
+ One problem that has been raised on the UIMA mailing lists is how to "push" documents into a UIMA processing pipeline. The simple answer with UIMA AS is to implement the processing pipeline as a UIMA AS service, and push requests from a custom application. Multiple instances of the processing pipeline service could be instantiated to increase throughput.
</p>
<p>
Included with UIMA AS is a sample application, RunRemoteAsyncAE. This application demonstrates most of the features of the new UIMA asynchronous API, including the ability to use a UIMA Collection Reader to push documents to a specified service.
@@ -287,6 +287,31 @@
<br>Figure 3 - Using RunRemoteAsyncAE to push documents into a UIMA AS service</br></td>
</tr></table>
</p>
+ <br />
+ <br />
+ <p>
+ A scaleout that corresponds to that provided by the Collection Processing Manager (CPM) is to have a single instance of collection reader and Cas Consumer(s) and scale out the other analysis components. Scaleout here is limited by the collection reader / Cas consumer bottleneck and the deserialization work required on the central driver. Scaleout efficiency is determined by the ratio of the processing done by the scaled out analysis engines to the serialization overhead in the services.
+ </p>
+ <p>
+ <table width="100%"><tr><td align="center" valign="middle">
+ <img src="./images/getting-started/singlecrscaleout.png" alt="Single Collection Reader Scaleout" border="0" />
+ <br>Figure 4 - Scaleout using a single set of Collection Reader and Cas Consumers</br></td>
+ </tr></table>
+ </p>
+ <br />
+ <br />
+ <p>
+ For very large scalability using UIMA AS, multiple copies of the collection reader and Cas consumers are needed. A central driver would distribute [references to] subsets of the input collection to the scaled out processing pipelines, where each pipeline contains a collection reader and the Cas consumers.
+ </p>
+ <p>
+ Scalout limitations in this scenario could be in several places, examples being a common source of input documents or a shared writable resource used by Cas consumers.
+ </p>
+ <p>
+ <table width="100%"><tr><td align="center" valign="middle">
+ <img src="./images/getting-started/multiplecrscaleout.png" alt="Very large Scaleout" border="0" />
+ <br>Figure 5 - Scaleout using multiple Collection Readers and Cas Consumers.</br></td>
+ </tr></table>
+ </p>
</blockquote>
</td></tr>
<tr><td><br/></td></tr>
Added: incubator/uima/site/trunk/uima-website/docs/images/getting-started/multiplecrscaleout.png
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/images/getting-started/multiplecrscaleout.png?rev=682240&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/uima/site/trunk/uima-website/docs/images/getting-started/multiplecrscaleout.png
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: incubator/uima/site/trunk/uima-website/docs/images/getting-started/runremoteasyncae.png
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/images/getting-started/runremoteasyncae.png?rev=682240&r1=682239&r2=682240&view=diff
==============================================================================
Binary files - no diff available.
Added: incubator/uima/site/trunk/uima-website/docs/images/getting-started/singlecrscaleout.PNG
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/docs/images/getting-started/singlecrscaleout.PNG?rev=682240&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/uima/site/trunk/uima-website/docs/images/getting-started/singlecrscaleout.PNG
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: incubator/uima/site/trunk/uima-website/xdocs/doc-uimaas-what.xml
URL: http://svn.apache.org/viewvc/incubator/uima/site/trunk/uima-website/xdocs/doc-uimaas-what.xml?rev=682240&r1=682239&r2=682240&view=diff
==============================================================================
--- incubator/uima/site/trunk/uima-website/xdocs/doc-uimaas-what.xml (original)
+++ incubator/uima/site/trunk/uima-website/xdocs/doc-uimaas-what.xml Sun Aug 3 18:57:39 2008
@@ -103,18 +103,41 @@
</p>
</subsection>
- <subsection name="UIMA AS - Example Application Scenario">
+ <subsection name="UIMA AS - Example Application Scenarios">
<p>
- One problem that has been raised on the UIMA mailing lists is how to "push" documents into a UIMA processing pipeline. The simple answer with UIMA AS is to implement the processing pipeline as a UIMA AS service, and push requests from a custom application. Multiple instances of the processing pipeline service could be instantiated to increase throughput. Note that the processing pipeline could itself contain a CAS Multiplier component so that a single request to the service could be a reference to collection of artifacts to be processed.
+ One problem that has been raised on the UIMA mailing lists is how to "push" documents into a UIMA processing pipeline. The simple answer with UIMA AS is to implement the processing pipeline as a UIMA AS service, and push requests from a custom application. Multiple instances of the processing pipeline service could be instantiated to increase throughput.
</p>
<p>
Included with UIMA AS is a sample application, RunRemoteAsyncAE. This application demonstrates most of the features of the new UIMA asynchronous API, including the ability to use a UIMA Collection Reader to push documents to a specified service.
- </p>
+ </p>
<p>
<table width="100%"><tr><td align="center" valign="middle">
<img src="./images/getting-started/runremoteasyncae.png" alt="RunRemoteAsyncAE application" border="0"/>
<br>Figure 3 - Using RunRemoteAsyncAE to push documents into a UIMA AS service</br></td>
</tr></table>
+ </p><br></br><br></br>
+
+ <p>
+ A scaleout that corresponds to that provided by the Collection Processing Manager (CPM) is to have a single instance of collection reader and Cas Consumer(s) and scale out the other analysis components. Scaleout here is limited by the collection reader / Cas consumer bottleneck and the deserialization work required on the central driver. Scaleout efficiency is determined by the ratio of the processing done by the scaled out analysis engines to the serialization overhead in the services.
+ </p>
+ <p>
+ <table width="100%"><tr><td align="center" valign="middle">
+ <img src="./images/getting-started/singlecrscaleout.png" alt="Single Collection Reader Scaleout" border="0"/>
+ <br>Figure 4 - Scaleout using a single set of Collection Reader and Cas Consumers</br></td>
+ </tr></table>
+ </p><br></br><br></br>
+
+ <p>
+ For very large scalability using UIMA AS, multiple copies of the collection reader and Cas consumers are needed. A central driver would distribute [references to] subsets of the input collection to the scaled out processing pipelines, where each pipeline contains a collection reader and the Cas consumers.
+ </p>
+ <p>
+ Scalout limitations in this scenario could be in several places, examples being a common source of input documents or a shared writable resource used by Cas consumers.
+ </p>
+ <p>
+ <table width="100%"><tr><td align="center" valign="middle">
+ <img src="./images/getting-started/multiplecrscaleout.png" alt="Very large Scaleout" border="0"/>
+ <br>Figure 5 - Scaleout using multiple Collection Readers and Cas Consumers.</br></td>
+ </tr></table>
</p>
</subsection>