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)" <ui...@incubator.apache.org> on 2008/07/07 15:29:32 UTC
[jira] Created: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Need a monitor component for UIMA-AS services to capture performance metrics
-----------------------------------------------------------------------------
Key: UIMA-1104
URL: https://issues.apache.org/jira/browse/UIMA-1104
Project: UIMA
Issue Type: New Feature
Components: Async Scaleout
Reporter: Jerry Cwiklik
In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein updated UIMA-1104:
--------------------------------
Attachment: idleWithRemote.txt
Looking much better. The attached log has a remote delegate. Not sure about how CASes are trickling out at the end.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-02.txt
Fixed how CASes are counted. The service should only count CASes coming from its input queue.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-13.txt
uimaj-as-activemq-UIMA-1104-patch-13.txt
Added support for reporting the depth of reply queues. Collocated services reply to one (common) internal reply queue that is associated with an aggregate service. The collocated service reply queue depth will be reported as -1. Changed the API for retrieving the input queue depth.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch-07.txt, uimaj-as-activemq-UIMA-1104-patch-09.txt, uimaj-as-activemq-UIMA-1104-patch-10.txt, uimaj-as-activemq-UIMA-1104-patch-11.txt, uimaj-as-activemq-UIMA-1104-patch-12.txt, uimaj-as-activemq-UIMA-1104-patch-13.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch-08.txt, uimaj-as-core-UIMA-1104-patch-09.txt, uimaj-as-core-UIMA-1104-patch-10.txt, uimaj-as-core-UIMA-1104-patch-12.txt, uimaj-as-core-UIMA-1104-patch-13.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-activemq-UIMA-1104-patch-11.txt
Fixed sun specific import if JMX OperatingSystemMXBean. Replaced it with a generic class from java.lang.management package
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch-07.txt, uimaj-as-activemq-UIMA-1104-patch-09.txt, uimaj-as-activemq-UIMA-1104-patch-10.txt, uimaj-as-activemq-UIMA-1104-patch-11.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch-08.txt, uimaj-as-core-UIMA-1104-patch-09.txt, uimaj-as-core-UIMA-1104-patch-10.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-10.txt
uimaj-as-activemq-UIMA-1104-patch-10.txt
Enhanced JMX Monitor to obtain free CAS instance count from Cas Multiplier's Cas Pool MBean.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch-07.txt, uimaj-as-activemq-UIMA-1104-patch-09.txt, uimaj-as-activemq-UIMA-1104-patch-10.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch-08.txt, uimaj-as-core-UIMA-1104-patch-09.txt, uimaj-as-core-UIMA-1104-patch-10.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-05.txt
uimaj-as-activemq-UIMA-1104-patch-05.txt
Removed debugging output from the code
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-12.txt
uimaj-as-activemq-UIMA-1104-patch-12.txt
Modified how the analysis time is aggregated and reported for JMX. Each time the JMX MBean asks for a current analysis time, the controller sums up the time of each processing thread and subtracts the time it takes to serialize and deserialize CASes. For aggregates, the analysis time is a sum of analysis times from all colocated delegates.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch-07.txt, uimaj-as-activemq-UIMA-1104-patch-09.txt, uimaj-as-activemq-UIMA-1104-patch-10.txt, uimaj-as-activemq-UIMA-1104-patch-11.txt, uimaj-as-activemq-UIMA-1104-patch-12.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch-08.txt, uimaj-as-core-UIMA-1104-patch-09.txt, uimaj-as-core-UIMA-1104-patch-10.txt, uimaj-as-core-UIMA-1104-patch-12.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS services to capture performance metrics
Posted by Jaroslaw Cwiklik <ui...@gmail.com>.
Marshall,
On Fri, Jul 11, 2008 at 11:26 AM, Marshall Schor <ms...@schor.com> wrote:
> I think these JVM -D parameters fall into 2 classes:
>
> 1) common to official sun jmx things (do they work on non- sun JVMs?) such
> as com.sun.management.jmxremote, etc.
>
>>>The enabling mechanism for JMX is the same as for UIMA core
described in section: Monitoring AE Performance using JMX
of Tutorials and User's Guides. I guess I need to test if
this works with IBM JVM.
>
> 2) things uima-as adds, such as jmx.monitor.frequency
>
> It seems to me that the (2) items should have collision-avoiding names,
> such as
> apache.uima.as.jmx.monitor.frequency.
>>> If this is a potential problem, than yes we may further disambiguate
this name by focusing this name more for use with UIMA-AS
>
> Jerry
> -Marshall
>
>
> Jerry Cwiklik (JIRA) wrote:
>
>> [
>> https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>>
>> Jerry Cwiklik updated UIMA-1104:
>> --------------------------------
>>
>> Attachment: uimaj-as-core-UIMA-1104-patch-06.txt
>> uimaj-as-activemq-UIMA-1104-patch-06.txt
>>
>> Integrated JmxMonitor with the UIMA_Service. Refactored UIMA_Service to
>> remove dead code.
>> The JmxMonitor startup is enabled via -Djmx.monitor.frequency=<number>
>> parameter. A presence of this parameter enables the monitor and redefines
>> monitor's default checkpoint frequency. Also, the monitor supports pluggable
>> formatter listeners. These listeners are called with new metrics every time
>> a checkpoint is completed. The listener may format the metrics to specific
>> requirements. To plug in a custom formatter use
>> -Djmx.monitor.formatter=<class name> parameter.
>>
>> An example command line setting for the JmxMonitor is as follows:
>> set UIMA_JVM_OPTS=-Dcom.sun.management.jmxremote
>> -Dcom.sun.management.jmxremote.port=8009
>> -Dcom.sun.management.jmxremote.authenticate=false
>> -Dcom.sun.management.jmxremote.ssl=false -Djmx.monitor.frequency=2000
>> -Djmx.monitor.formatter=org.apache.uima.examples.as.DefaultUimaServiceMonitorFormatter
>>
>> Note: the custom formatter class is instantiated using default (empty)
>> constructor.
>>
>>
>>
>>
>>
>>> Need a monitor component for UIMA-AS services to capture performance
>>> metrics
>>> -----------------------------------------------------------------------------
>>>
>>> Key: UIMA-1104
>>> URL: https://issues.apache.org/jira/browse/UIMA-1104
>>> Project: UIMA
>>> Issue Type: New Feature
>>> Components: Async Scaleout
>>> Reporter: Jerry Cwiklik
>>> Attachments: idleWithRemote.txt,
>>> uimaj-as-activemq-UIMA-1104-patch-03.txt,
>>> uimaj-as-activemq-UIMA-1104-patch-04.txt,
>>> uimaj-as-activemq-UIMA-1104-patch-05.txt,
>>> uimaj-as-activemq-UIMA-1104-patch-06.txt,
>>> uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt,
>>> uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt,
>>> uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt,
>>> uimaj-as-core-UIMA-1104-patch.txt
>>>
>>>
>>> In complex uima-as deployments it is hard to find bottlenecks which need
>>> scaleup. A JMX-based monitor is needed to collect runtime metrics from every
>>> uima-as service. The metrics must include idle time, queue depth, amount of
>>> time each service waits for a free CAS. The monitor should be an embeddable
>>> component that can be deployed in a java application. The monitor should
>>> allow custom formatting of metrics via pluggable extension.
>>>
>>
>>
>>
>
>
Re: [jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by Marshall Schor <ms...@schor.com>.
I think these JVM -D parameters fall into 2 classes:
1) common to official sun jmx things (do they work on non- sun JVMs?)
such as com.sun.management.jmxremote, etc.
2) things uima-as adds, such as jmx.monitor.frequency
It seems to me that the (2) items should have collision-avoiding names,
such as
apache.uima.as.jmx.monitor.frequency.
-Marshall
Jerry Cwiklik (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jerry Cwiklik updated UIMA-1104:
> --------------------------------
>
> Attachment: uimaj-as-core-UIMA-1104-patch-06.txt
> uimaj-as-activemq-UIMA-1104-patch-06.txt
>
> Integrated JmxMonitor with the UIMA_Service. Refactored UIMA_Service to remove dead code.
> The JmxMonitor startup is enabled via -Djmx.monitor.frequency=<number> parameter. A presence of this parameter enables the monitor and redefines monitor's default checkpoint frequency. Also, the monitor supports pluggable formatter listeners. These listeners are called with new metrics every time a checkpoint is completed. The listener may format the metrics to specific requirements. To plug in a custom formatter use -Djmx.monitor.formatter=<class name> parameter.
>
> An example command line setting for the JmxMonitor is as follows:
> set UIMA_JVM_OPTS=-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8009 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djmx.monitor.frequency=2000 -Djmx.monitor.formatter=org.apache.uima.examples.as.DefaultUimaServiceMonitorFormatter
>
> Note: the custom formatter class is instantiated using default (empty) constructor.
>
>
>
>
>> Need a monitor component for UIMA-AS services to capture performance metrics
>> -----------------------------------------------------------------------------
>>
>> Key: UIMA-1104
>> URL: https://issues.apache.org/jira/browse/UIMA-1104
>> Project: UIMA
>> Issue Type: New Feature
>> Components: Async Scaleout
>> Reporter: Jerry Cwiklik
>> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch.txt
>>
>>
>> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
>>
>
>
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-06.txt
uimaj-as-activemq-UIMA-1104-patch-06.txt
Integrated JmxMonitor with the UIMA_Service. Refactored UIMA_Service to remove dead code.
The JmxMonitor startup is enabled via -Djmx.monitor.frequency=<number> parameter. A presence of this parameter enables the monitor and redefines monitor's default checkpoint frequency. Also, the monitor supports pluggable formatter listeners. These listeners are called with new metrics every time a checkpoint is completed. The listener may format the metrics to specific requirements. To plug in a custom formatter use -Djmx.monitor.formatter=<class name> parameter.
An example command line setting for the JmxMonitor is as follows:
set UIMA_JVM_OPTS=-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8009 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Djmx.monitor.frequency=2000 -Djmx.monitor.formatter=org.apache.uima.examples.as.DefaultUimaServiceMonitorFormatter
Note: the custom formatter class is instantiated using default (empty) constructor.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611588#action_12611588 ]
Eddie Epstein commented on UIMA-1104:
-------------------------------------
Jerry,
Something wrong with the stats below. Scenario was:
service = Deploy_MeetingDetectorTAE_Sync_3Instances.xml
client = runremoteasyncae tcp://localhost:61616 MeetingDetectorTaeQueue -c ManyDocsCollectionReader.xml -p 15 -f 100000
ManyDocsCollectionReader.xml is pointing a directory with a few thousand documents with sizes ranging from 1000-10000 chars.
INFO: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Jul 8, 2008 9:51:31 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 6,855 [ TutorialDateTime Annotator_Service Performance ] Idle 1,021 CASes 0 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:31 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 6,855 [ Meeting Detector TAE_Service Performance ] Idle 1,022 CASes 0 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:31 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 6,855 [ Room Number Annotator_Service Performance ] Idle 1,020 CASes 0 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:31 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 6,855 [ Meeting Annotator_Service Performance ] Idle 1,020 CASes 0 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:31 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Jul 8, 2008 9:51:32 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 7,889 [ TutorialDateTime Annotator_Service Performance ] Idle 1,032 CASes 7 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:32 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 7,889 [ Meeting Detector TAE_Service Performance ] Idle 1,140 CASes 7 InQDepth 0 SCP Wait 24 CMgetNext 0
Jul 8, 2008 9:51:32 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 7,889 [ Room Number Annotator_Service Performance ] Idle 1,032 CASes 7 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:32 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 7,889 [ Meeting Annotator_Service Performance ] Idle 1,046 CASes 7 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:32 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Jul 8, 2008 9:51:33 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 8,948 [ TutorialDateTime Annotator_Service Performance ] Idle 1,043 CASes 62 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:33 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 8,948 [ Meeting Detector TAE_Service Performance ] Idle 41,553 CASes 65 InQDepth 9 SCP Wait 427 CMgetNext 0
Jul 8, 2008 9:51:33 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 8,948 [ Room Number Annotator_Service Performance ] Idle 884 CASes 64 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:33 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
INFO: Timestamp: 8,948 [ Meeting Annotator_Service Performance ] Idle 1,051 CASes 61 InQDepth 0 SCP Wait 0 CMgetNext 0
Jul 8, 2008 9:51:33 AM org.apache.uima.aae.jmx.monitor.JmxMonitorListener run
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-03.txt
uimaj-as-activemq-UIMA-1104-patch-03.txt
Modified UIMA-AS service to call endProcess() if the service is not a Cas Multiplier. Fixes invalid idleTime.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-08.txt
Fixed the code that aggregates time spent waiting for CASes on a Cas Pool and a Shadow Cas Pool.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch-07.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch-08.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-09.txt
uimaj-as-activemq-UIMA-1104-patch-09.txt
Modified to use more accurate thread timer. The thread CPU utilization is retrieved from the JVM MXBean. In case the JVM MXBean does not provide per thread timing info, a wall clock is still used. Removed time waiting in GetNext from the metrics, since it does not provide an accurate measure. Since the thread is sleeping while waiting (in getNext()) for a free CAS, the CPU utilization will be 0. Added two new attributes to the service metrics: threadCount which indicates number of process threads, and the analysis time which is time spent analyzing a CAS (for primitives). The Aggregate sums up all analysis times reported by its collocated delegates.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch-07.txt, uimaj-as-activemq-UIMA-1104-patch-09.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch-08.txt, uimaj-as-core-UIMA-1104-patch-09.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-activemq-UIMA-1104-patch-07.txt
Changes to enable integration of JmxMonitor with the UIMA AS service wrapper
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch-07.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch.txt
uimaj-as-activemq-UIMA-1104-patch.txt
Created a new uima-as component to capture runtime metrics of uima-as services. The monitor connects to a JMX server via provided URI and begins checkpoints at a given intervals each time collecting metrics from JMX service beans. The monitor supports plug in listener that are notified each time the checkpoint is done. The listener receives the metrics for the current checkpoint (interval). The listener can format the metrics to specific requirements.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1104:
--------------------------------
Attachment: uimaj-as-core-UIMA-1104-patch-04.txt
uimaj-as-activemq-UIMA-1104-patch-04.txt
Fixed idle time for remotes
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1104) Need a monitor component for UIMA-AS
services to capture performance metrics
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eddie Epstein closed UIMA-1104.
-------------------------------
Resolution: Fixed
Finally looks good. Any further changes should have specific issues created.
> Need a monitor component for UIMA-AS services to capture performance metrics
> -----------------------------------------------------------------------------
>
> Key: UIMA-1104
> URL: https://issues.apache.org/jira/browse/UIMA-1104
> Project: UIMA
> Issue Type: New Feature
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Attachments: idleWithRemote.txt, uimaj-as-activemq-UIMA-1104-patch-03.txt, uimaj-as-activemq-UIMA-1104-patch-04.txt, uimaj-as-activemq-UIMA-1104-patch-05.txt, uimaj-as-activemq-UIMA-1104-patch-06.txt, uimaj-as-activemq-UIMA-1104-patch-07.txt, uimaj-as-activemq-UIMA-1104-patch-09.txt, uimaj-as-activemq-UIMA-1104-patch-10.txt, uimaj-as-activemq-UIMA-1104-patch-11.txt, uimaj-as-activemq-UIMA-1104-patch-12.txt, uimaj-as-activemq-UIMA-1104-patch-13.txt, uimaj-as-activemq-UIMA-1104-patch.txt, uimaj-as-core-UIMA-1104-patch-02.txt, uimaj-as-core-UIMA-1104-patch-03.txt, uimaj-as-core-UIMA-1104-patch-04.txt, uimaj-as-core-UIMA-1104-patch-05.txt, uimaj-as-core-UIMA-1104-patch-06.txt, uimaj-as-core-UIMA-1104-patch-08.txt, uimaj-as-core-UIMA-1104-patch-09.txt, uimaj-as-core-UIMA-1104-patch-10.txt, uimaj-as-core-UIMA-1104-patch-12.txt, uimaj-as-core-UIMA-1104-patch-13.txt, uimaj-as-core-UIMA-1104-patch.txt
>
>
> In complex uima-as deployments it is hard to find bottlenecks which need scaleup. A JMX-based monitor is needed to collect runtime metrics from every uima-as service. The metrics must include idle time, queue depth, amount of time each service waits for a free CAS. The monitor should be an embeddable component that can be deployed in a java application. The monitor should allow custom formatting of metrics via pluggable extension.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.