What should one check if the CIM Application Performance is slow?

Customer Interaction Manager, Real-Time Interaction Manager, TD Channel Integration Services
Teradata Employee

What should one check if the CIM Application Performance is slow?

What should one check if the CIM Application Performance is slow? 

Tags (2)
Teradata Employee

Re: What should one check if the CIM Application Performance is slow?

CIM Application performance relates directly to the performance of the Database, Network, and environment it is running in. You will want to review the What are the Best Practices for CIM Performance topic in the forum.


If you are experiencing CIM application slowdowns, there are a number of things that you can check.


1.) Check the CIM logging to help identify area of performance issues.

The trm-system.log and PE logs can help aid in troubleshooting performance issues. SQL and timing logging can be enabled via the log4j.xml file as outlined in Knowledge Article KCS005545.


For Online/Navigation/GUI Performance Issues:

 The logger named "jdbc.sqltiming" set to INFO (as noted in KCS005545), will capture valuable timing information in the trm-system.log for the CIM requests such as below:


<-- End /trm/job.do index Total Time=63046, Appsvr Time=7160, Database Time=55886, SqlCount=6


This example shows that the request took ~63 seconds (63046 milliseconds). There were 6 sqls sent to the database which took ~56 seconds to execute in the database alone. These sqls should be sub second queries and you can see in this example, the majority of the total time was in the database. In this case the DBA should address the database performance to improve the CIM experience.


 For Offline Performance Issues:

 For Offline Performance Issues, timing information can be found in the PE logs themselves after the individual sql queries. If the logging has been enabled, you can see a time logged after the query such as the below:


{executed in 65974 msec}


It is suggested to find the longest running queries and work from there. If you do not see long running queries, the logs can be reviewed for time gaps or etc.


2.) Check the database Canary Query timings to see if your slow performance coincides with longer times to execute the canary query. (See KCS article KCS005544 for more details on setting up canary queries.) If so, the DBA would need to address the workload or database performance issues. 


3.) Have the DBA check the DBQL for the timeframe of performance issues to see if there are database performance issues in executing the sqls.


4.) Check with the DBA to see if other processes are running on the database such as backup jobs, ETL jobs, or etc.


5.) Check with the DBA to see if there have been any recent data model changes (i.e. new view, columns, etc.)


6.) Check with the CIM Administrator to determine if there have been any recent mapping changes to CIM.


7.) Check with your Network team to monitor the network connections from clients/servers and server/database for performance


8.) Check the application server logs for any errors or issues


If you are still unable to pinpoint the area of the performance issue, an incident can be opened via T@YS. Please capture and provide the information found from the above steps in addition to the CIM checklist items and further investigation can be completed.

Tags (2)