This document provide some guidelines and suggestions to help improve the performance for CA Service Catalog
Following is the recommendation for fine tuning the Service Catalog
| PARAMETER | Setting | Units |
| Tomcat Threads | 800 | number |
| Tomcat connection timeout | 1000000 | milliseconds |
| Java initial Heap Size | 512 | MB |
| Java maximum Heap Size | 2048 | MB |
| Connection Pool Size | 300 |
File Location for the above modifications
Java Heap
Viewservice.conf located in USM_HOME\view\conf
Tomcat
Server.xml located in USM_HOME\view\conf
Connection pool
Config.properties located in USM_HOME
The Maximum heap size for Java could be 1/4 of the physical memory on the server assuming that the Service Catalog is the only application installed on the server
The information in this article has been included in our product documentation. You can find further details here:
https://docops.ca.com/ca-service-management/14-1/en/using/service-catalog-management/best-practices-for-service-catalog-management/best-practices-foundation
Recommendations for 14.1.05 and later:
https://docops.ca.com/ca-service-management/14-1/en/implementing/implementing-ca-service-management-14-1-05/post-install-tasks-for-ca-service-management-14-1-05/post-install-steps-for-ca-service-catalog-14-1-05
Recommendations for 17.1 and later:
https://docops.ca.com/ca-service-management/17-1/en/troubleshooting/troubleshooting-ca-service-catalog/ca-service-catalog-performance-tuning