How do I speed up performance in the AppManager Control Center? (NETIQKB44767)

How do I speed up performance in the AppManager Control Center?

Causes of Slow Performance

As environments grow larger and larger, a common question for the Operator Console is how to make the console load more quickly. The answer focuses on limiting the number of objects and datapoints displayed.

AppManager Control Center works in a similar way. As AppManager Control Center was built to display huge amounts of information from hundreds or thousands of systems, a caching mechanism is part of the console architecture.

Running AppManager Control Center on a  system with robust specifications (especially memory) will improve speed. However, the cause of any display lag is often cache refresh.

In order for your settings to follow you from one location to another, cached information is maintained in the CCDB repository (as opposed to a local cache at each workstation). Information retained in the cache repository includes events, jobs and servers. All of this information must transfer from the repository to the console for display.

There are several ways to avoid refreshing and loading data that you do not need for the moment.

Resolutions

1.  Filter unnecessary information: When you filter a View in the grid by the contents of a column (field), you hide the data, but it is still cached and downloaded. AppManager Control Center allows you to apply filters as part of each view to keep it from downloading. You can access a "View Filter" in the Properties tab for each View. 
2. Delete tabs in the Server Information pane: You can have many personalized views with only the information you need for a specific set of tasks. You can reduce the data downloading required for your "favorite views" by tuning what gets displayed. There are times when you select a group of servers (Server View) for a purpose that does not include viewing data in the Server Information pane. For example, if you select a number of servers so that you can create a new job on all of them, you have no interest in seeing all the events for those servers in the Events tab of the Server Information pane. You can avoid downloading the events in two ways:
   • Open the Server View Properties dialog box, select the Server Information tab, and uncheck the Show Events box.
   • Open the Options dialog box from the Tools menu, choose Servers in the tree at the left and enter a small number in the "Events for more than" text box on the right.
3. Delete child events in a Split Parent/Child View: When you select a large number of parent events in a split Parent/Child View, data for all the child events of all the selected parent events is loaded into the child events list in the bottom of the View pane. There are times when you do not need to load these child events. For example, if you select a number of parent events so that you can close them all at once, you have no interest in seeing all the child events. You can avoid downloading the child events in three ways:
   • In the Tasks pane or the right-click pop-up menu, choose Hide Children of Selected Parents. Do this before you select multiple parents.
   • Open the Events Properties dialog box to the General tab and select the Show Parent Events radio button.
   • Open the Options dialog box from the Tools menu, choose Events in the tree at the left and enter a small number in the text box in the Performance Options section. Note: Unless you need to see both parents and children.
     simultaneously, you will get better performance by viewing only parent events or only child events. (Set this in the General tab of the Event Properties dialog box.) 
4. Limit Caching for Management Groups: In the Cache tab of the Management Group Properties dialog box, you choose which events and jobs you want the Cache Manager to synchronize (that is, update to reflect changes that may have occurred in the managed repositories) for that particular Management Group. The default settings are to synchronize only open and acknowledged events and to synchronize all jobs except those that are closed. Performance will be best when the Cache Manager synchronizes the minimum amount of data.

Formerly known as NETIQKB44767