Jerry Cwiklik created UIMA-2518:
-----------------------------------
Summary: UIMA-AS stats logged in uima.log are wrong
Key: UIMA-2518
URL: https://issues.apache.org/jira/browse/UIMA-2518
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Affects Versions: 2.4.0AS
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
Priority: Minor
Fix For: 2.4.1AS
UIMA-AS aggregate service logs stats in uima log that seem not correct.
Especially, process times seem bogus. Check how the process times are managed
and reported. Also, check the validity of deserialization and serialization
times as well. An example stats look as follows:
10:00:42.802 - 8:
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.logStats:
INFO: Controller: [Test Aggregate TAE] Delegate <<NoOp>> Stats:
Total Number CASes Processed: 10
Total CAS Deserialization Time: 46.875 ms
Total CAS Serialization Time: 15.625 ms
Total Time Spent In Analysis: 296.875 ms
Max Serialization Time: 15.625 ms
Max Deserialization Time: 15.625 ms
Max Analysis Time: 234.375 ms
Total Idle Time: 6,610.507 ms
10:00:42.818 - 8:
org.apache.uima.aae.controller.AggregateAnalysisEngineController_impl.logStats:
INFO: Controller: [Test Aggregate TAE] Delegate <<Test Aggregate TAE>> Stats:
Total Number CASes Processed: 10
Total CAS Deserialization Time: 15.625 ms
Total CAS Serialization Time: 62.5 ms
Total Time Spent In Analysis: 109.375 ms
Max Serialization Time: 15.625 ms
Max Deserialization Time: 15.625 ms
Max Analysis Time: 234.375 ms
Total Idle Time: 1,949.922 ms
The numbers reported dont add up. For example, the Max Analysis Time exceeds
the Total Time Spent in Analysis which makes no sense.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
