Re: Correlated situation overhead on ITM HTEMS
John Alvord <jalvord-r/[email protected]>
| Newsgroups | gmane.comp.sysutils.tivoli.general |
|---|---|
| Message-ID | <OF811430D7.C184BB4C-ON88257B2E.00765A6C-88257B2E.00766A80__33170.8193793476$1363296866$gmane$org@us.ibm.com> |
Be very wary... TEMS Storage Growth and Correlated Situations http://www.ibm.com/support/docview.wss?uid=swg21579095 Regards, John Alvord - Ph: 1-720-396-2788 Cell: none Customer Support - Tivoli Software - jalvord-r/[email protected] Advisory Engineer - Tivoli Monitoring - ITM infrastructure Follow us on Twitter! @Tivolisupport and Facebook Personalize your support needs with the IBM Support Portal Use Service Request to get assistance! For emails regarding a PMR, copy [email protected] For secure browser uploads: https://www.ecurep.ibm.com/app/upload For Customer Support guidance: IBM Software Support Handbook From: "Redus, James E CIV DISA CSD (US)" <[email protected]> To: "Discussion list for Tivoli product and Tivoli Ready products." <[email protected]>, Date: 03/14/2013 02:12 PM Subject: [TME10] Correlated situation overhead on ITM HTEMS Sent by: [email protected] Hi List. A question came up recently about the growing number of ITM Correlated Situations running in our environ. These SITs run on the HTEMS, and we?d like to know if they consume a significant amount of HTEMS resources, and if so, what is a reasonable number to have running? Currently we have about 2 dozen correlated SITS. I would think that since correlated SITs are based on a comparison of true/false values from other SITs, that the HTEMS is probably not sifting thru much data and could handle a pretty good number of these. We have a pretty healthy 24-CPU, 16GB mem Sparc Solaris HTEMS, with a load avg that rarely goes above 2, and about 6400 OS agents in the environ (ITM 622, FP5). Any experiences running a large number of correlated SITs? Thanks in advance, -James _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected] _______________________________________________ TME10 mailing list [email protected] Unsubscribe:[email protected]