[
https://issues.apache.org/jira/browse/UIMA-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567673#action_12567673
]
Jerry Cwiklik commented on UIMA-755:
------------------------------------
Modified code to extract stats from the reply msg and fill the ProcessTrace
object before notifying the application via entityProcessComplete. The second
arg in this method contains the ProcessTrace object and the application can
extract all events by calling:
aProcessStatus.getProcessTrace().getEventsByComponentName("UimaEE",
false);
Note that the events have a fixed component name "UimaEE". The application can
extract individual events by traversing the list of events:
List eList =
aProcessStatus.getProcessTrace().getEventsByComponentName("UimaEE", false);
for( int i=0; i < eList.size(); i++)
{
ProcessTraceEvent eEvent = (ProcessTraceEvent)eList.get(i);
System.out.println("eEvent.getDescription()+"
Duration::"+eEvent.getDuration()+" ms");
....
An example output produced:
Total Time Waiting For Reply Duration::6033 ms
Time To Serialize Cas Duration::2 ms
Time To Deserialize Cas Duration::10 ms
Time to Wait for CAS Duration::0 ms
Total Time In Process CAS Duration::6002 ms
Idle Time Waiting For CAS Duration::0 ms
> Expose per CAS statistics to the application from uima-as client
> ----------------------------------------------------------------
>
> Key: UIMA-755
> URL: https://issues.apache.org/jira/browse/UIMA-755
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Affects Versions: 2.2.1
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-test-resources-UIMA-755-patch.txt,
> uimaj-as-activemq-test-src-UIMA-755-patch.txt,
> uimaj-as-activemq-UIMA-755-patch.txt, uimaj-as-core-UIMA-755-patch.txt,
> uimaj-as-jms-UIMA-755-patch.txt
>
>
> Modify the uima-as client to pass per CAS statistics via the
> entityProcessComplete callback. Use ProcessTrace object as a container for
> statistics. Statistics to be passed to the application include: time spent in
> process, time spent serializing CAS, time spent de-serializing CAS, service
> idle time, service host ip, CAS latency (total time spent waiting for reply)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
