Troubleshooting AIS performance problems.

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Atrium CMDB Suite


    BMC Atrium CMDB Suite



    AIS Simulation runs for nearly 45 minutes to display the results for CI's with large number of relationships

    LP: BMC Atrium CMDB Suite





    Legacy ID:KA403744


    One thing the customer can try first is increasing the number of threads of the shared plugin.
    To do that modify the pluginsvr_config.xml file from AtriumCore/cmdb/plugins/shared folder.

    Increase in this line from 5 to 10 to check if there is a better performance.

    Once this is done the next step is finding out what other bottlenecks we have. The bottleneck could be at ARS (thread count may be too low) so ARS takes long time to reply to AIS. This can be found out by making API/SQL analysis of ARS through ARLogAnalyzer.

    During this test you can also monitor Memory and CPU usage of ARS box. If either is reaching its maximum then a hardware increase is needed.

    If ARS is responding well to the test, and APIs return quickly but the SQL is the slow part then we need to start working at the DB level.
    DB analysis needs to be run to find out if any additional indexes are needed or special maintenance (like defragmentation).

    At this time you can also monitor DB usage of CPU/RAM to check if DB hardware needs an increase.

    Related Products:  
    1. BMC Atrium CMDB Suite


    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles