Improve Performance of TEP
ReggieHubbard 060000P2W2 Visits (2162)
Dear Rocky' answers your System z monitoring and performance tuning questions. Rocky McMahan, a Senior Software Performance Engineer in Tivoli R&D, offers valuable tips to help you get more out of your Tivoli monitoring software.
I am a System's Programmer for a large specialty insurance company with over $100 billion in total assets and approximately 65,000 employees.We run various IBM® Tivoli® OMEGAMON® products to monitor our 4 - way production Parallel Sysplex running z/OS® 1.12, IMS®V11, CICS® 4.2, DB2® V9 , and WebSphere® for Messaging.
Our Operation's staff closely monitors the health of our Enterprise by relying on the Tivoli Enterprise Portal(TEP). In particular, they pay close attention on the CPU usage of our Tivoli Enterprise Monitoring Agent (TEMA) and Tivoli Enterprise Monitoring Server(TEMS).
There are times when we observe high CPU usage of the various TEMAs & TEMS. This occurs even when only a few users are logged into the TEP. We were wondering if you had any suggestions that might help us reduce the TEP impact on the CPU usage of our TEMAs and TEMS?
Wondering in Wyoming.
Dear Wondering in Wyoming,
Users logged into the TEP can have a significant impact on the CPU usage of the TEMAs and TEMS, depending on the workspace and the amount of data being displayed.
Here's an example;
OMEGAMON XE for Mainframe Networks has a TN3270 Server Sessions workspace in the TEP that can display information about TN3270 sessions which are active, as well as sessions that have ended. For a large TN3270 environment, that could be a very large amount of data. Each time the workspace is refreshed, there will be a CPU usage cost to both the TEMA and the TEMS. By default, this particular workspace has a refresh interval of 60 seconds. If a user is logged onto the TEP and has navigated to this workspace, the workspace will be refreshed every 60 seconds. If the TEP user navigates away from this workspace and pauses the refresh, the cost of refreshing that workspace is suspended.
So CPU usage can be reduced by carefully choosing which workspaces to display. You also have the option of changing the refresh interval of a workspace. By changing the refresh interval from 60 seconds to 5 minutes, the CPU usage cost to the TEMA and TEMS could be reduced by as much as 70%.
We are not recommending that you change your refresh intervals - just providing an example which illustrates the cost of gathering data more frequently. It is up to you to review your business needs and determine if your refresh intervals are set appropriately for TEP workspaces.
Some workspaces may display large amounts of data - thus increasing CPU usage dramatically if the user continues to display a particular workspace and the refresh interval causes a high frequency of queries to be generated. If a user remains logged on to the TEP for extended periods, be conscious of which workspace(s) are displayed.
Many thanks to Glenn Crawford for his contributions to this article.