Cisco Cisco Tidal Enterprise Scheduler 6.2 Brochure
3
Cisco Tidal Enterprise Scheduler 6.2 Performance Tuning Guide
OL-32251-01
Cisco Tidal Enterprise Scheduler 6.2 Performance Tuning Guide
Monitoring with JConsole
Performance Matrix
The tables below help you link common catalysts that impact performance with the areas that need to be
monitored/tuned to get better performance.
monitored/tuned to get better performance.
For example, in the table above, if you are experiencing performance problems with large schedules, the
items you should tune or monitor would be the CPU, the memory, your JMS, and the Cache Write.
items you should tune or monitor would be the CPU, the memory, your JMS, and the Cache Write.
Monitoring with JConsole
JConsole is a diagnostic tool that comes with the standard JDK. It allows you to connect directly to a
running JVM and monitor many performance metrics, including memory/CPU usage. JConsole can also
be used to access diagnostic modules exposed by each individual application called MBeans. Both the
Master and Client Manager expose MBeans.
running JVM and monitor many performance metrics, including memory/CPU usage. JConsole can also
be used to access diagnostic modules exposed by each individual application called MBeans. Both the
Master and Client Manager expose MBeans.
Connecting JConsole
Before connecting JConsole to either the Client Manager or Master, make sure the following property is
set in clientmgr.props or master.props.
set in clientmgr.props or master.props.
JmxOn=Y
Table 1-1
Client Manager and DSP Performance Matrix
Catalyst
CPU
Memory
JMS
Cache
Read
Read
Cache
Write
Write
Cache
Tuning
Tuning
Cache
Sync
Sync
Users
X
X
X
X
X
Schedule Activity
X
X
X
X
Schedule Compile X
X
X
X
Cache Sync
X
X
X
X
X
Table 1-2
Master Performance Matrix
Catalyst
CPU
Memory
JMS
DB Connections
Message Threads
Client Managers
X
X
X
X
X
Adapter
Connections
Connections
X
X
X
Agents
X
X
X
Schedule Activity
X
X
X
X
X
Schedule Compile
X
X
X
X
Definitions
X
X
Logs and History
X
Cache Sync
X
X
X
X
X