TSIM performance is very slow and jserver is consuming high levels of CPU. We are not able to access the GUI and create generate incidents. There are times when we login to the TSIM server and attempt to generate incidents the GUI is non-responsive.
Certain performance problems can be observed within the navigation tree of the Ops Console. Examples of this could be:
Navigation tree does not load at all
Navigation tree only partially loads
Navigation tree takes a long time to load
Operations Console becomes inaccessible and the number of https processes increases
Setting the lazy loading parameter to true can help to resolve these problems.
High number of events
High number of dynamic collectors
High number of CIs in the service model
Depth of service model
Large number of component folders
Large number of event folders
Our recommendation is for users to uncheck those items in the navigation tree preferences that they are not interested in. For example, if a user is interested in events only, then uncheck the boxes related to service model and folders.
This is because of the way the navigation tree works, in that data is loaded in the order of top to down. So, it will be event collectors first, then groups, then service model CIs, then component folders, then event folders. All of this can take time as they have to be loaded from various sources such as cell, jserver, backend database, and it can result in a bottleneck.
The lazyloading option says to load only the toplevel elements. Then as soon as a user wishes to expand that toplevel it will fetch the data at that point. That is why traversing from toplevel down can seem slower, but it is greatly reducing the load on the jserver.
To turn the lazyloading option on, add the following property to pw/custom/conf/pronet.conf file:
Then reload the jserver properties with command:
pw jproperties reload