You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2011/07/22 21:52:57 UTC

[jira] [Created] (UIMA-2180) UIMA AS primitive service should return performance breakdown for each CAS

UIMA AS primitive service should return performance breakdown for each CAS
--------------------------------------------------------------------------

                 Key: UIMA-2180
                 URL: https://issues.apache.org/jira/browse/UIMA-2180
             Project: UIMA
          Issue Type: New Feature
          Components: Async Scaleout
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik
             Fix For: 2.3.2AS


Current UIMA AS code doesnt extract CAS per component performance breakdown from UIMA aggregate. Such breakdown would be very useful in identifying bottlenecks in a pipeline. This breakdown is available via AnalysisEngine's getManagementInterface(). The API accesses the same performance stats that AE exposes via JMX. Since these stats are cumulative, the UIMA AS code should calculate delta to obtain per CAS performance breakdown. Before calling processAndOutputNewCASes(), the code should make a copy (actually a deep copy) of AnalysisEngineManagement instance(s) and calculate delta (of analysisTime) before returning input CAS.
The list containing the breakdown should be serialized into a reply message and de-serialized by the client. The UIMA AS client will provide an application the breakdown as a List via a callback method on UimaAsBaseCallbackListener. 


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (UIMA-2180) UIMA AS primitive service should return performance breakdown for each CAS

Posted by "Jerry Cwiklik (Commented) (JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168614#comment-13168614 ] 

Jerry Cwiklik commented on UIMA-2180:
-------------------------------------

Extended UIMA AS client API to include 
public String sendAndReceiveCAS(CAS aCAS, List<AnalysisEnginePerformanceMetrics> componentMetricsList) throws ResourceProcessException;
to provide application with per AE performance breakdown.
                
> UIMA AS primitive service should return performance breakdown for each CAS
> --------------------------------------------------------------------------
>
>                 Key: UIMA-2180
>                 URL: https://issues.apache.org/jira/browse/UIMA-2180
>             Project: UIMA
>          Issue Type: New Feature
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.4.0AS
>
>
> Current UIMA AS code doesnt extract CAS per component performance breakdown from UIMA aggregate. Such breakdown would be very useful in identifying bottlenecks in a pipeline. This breakdown is available via AnalysisEngine's getManagementInterface(). The API accesses the same performance stats that AE exposes via JMX. Since these stats are cumulative, the UIMA AS code should calculate delta to obtain per CAS performance breakdown. Before calling processAndOutputNewCASes(), the code should make a copy (actually a deep copy) of AnalysisEngineManagement instance(s) and calculate delta (of analysisTime) before returning input CAS.
> The list containing the breakdown should be serialized into a reply message and de-serialized by the client. The UIMA AS client will provide an application the breakdown as a List via a callback method on UimaAsBaseCallbackListener. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (UIMA-2180) UIMA AS primitive service should return performance breakdown for each CAS

Posted by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-2180.
-------------------------------

    Resolution: Fixed

Modified PrimitiveAnalysisEngineController to extract per component performance breakdown provided by UIMA aggregate. The breakdown is then attached to a reply message and reported to an application client via a new (overloaded)entityProcessComplete method. The new method exposes the breakdown in List<AnalysisEnginePerformanceMetrics> argument. Updated docbooks.

> UIMA AS primitive service should return performance breakdown for each CAS
> --------------------------------------------------------------------------
>
>                 Key: UIMA-2180
>                 URL: https://issues.apache.org/jira/browse/UIMA-2180
>             Project: UIMA
>          Issue Type: New Feature
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.3.2AS
>
>
> Current UIMA AS code doesnt extract CAS per component performance breakdown from UIMA aggregate. Such breakdown would be very useful in identifying bottlenecks in a pipeline. This breakdown is available via AnalysisEngine's getManagementInterface(). The API accesses the same performance stats that AE exposes via JMX. Since these stats are cumulative, the UIMA AS code should calculate delta to obtain per CAS performance breakdown. Before calling processAndOutputNewCASes(), the code should make a copy (actually a deep copy) of AnalysisEngineManagement instance(s) and calculate delta (of analysisTime) before returning input CAS.
> The list containing the breakdown should be serialized into a reply message and de-serialized by the client. The UIMA AS client will provide an application the breakdown as a List via a callback method on UimaAsBaseCallbackListener. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira