Reduce CPU% of TEMS using duperization
ReggieHubbard 060000P2W2 Visits (6514)
'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 performance engineer for a large global health services company with over 32,00 employees, operates in 30 countries
Dear Concerned in Connecticut,,
Be careful when setting up your situations. With Tivoli Enterprise Portal, you can set different intervals
for every situation. However, having several different intervals can increase the CPU% processing requirement
of the TEMS. This additional processing can be significant, depending on the number of the started situations
for an attribute group. By using the same interval for multiple situations, it is possible to reduce the
processing required to handle the situations.
How is this accomplished?
To reduce the sampling overhead, the Tivoli Enterprise Monitoring Server (TEMS) uses an optimization method
called situation synchronization, also known as duper or duperization, to group situation sampling requests
together. Therefore only one sampling is performed for a set of situations that sample the same attributes
at the same interval. By using the same interval for several situations, you may be able to reduce your CPU
usage in both your agent, as well as your TEMS.
You should verify that CMS_DUPER is set to YES, which is the default. This parameter enables situation synchronization.
Many thanks to Glenn Crawford for his contributions to this article.