uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: [jira] Updated: (UIMA-1104) Need a monitor component for UIMA-AS services to capture performance metrics
Date Fri, 11 Jul 2008 15:26:09 GMT
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. 
>>     
>
>   


Mime
View raw message