Symptoms and Causes of Inefficient Cache Usage
Determining the symptoms and causes of inefficient cache usage might help troubleshoot your system.
- Slow-running business processes
- Longer completion time for business processes
- Reduced number of cache hits, as reported in the Cache Usage Report, with a corresponding increase in the number of requests.
Determining the reasons behind the inefficient use of cache may require you to investigate many areas of your system and the way you are implementing Sterling B2B Integrator.
- Improperly tuned performance properties
- High cache usage for less frequently used large objects
- Low cache usage for frequently used small objects
To determine the reason behind the inefficient use of cache, review the Cache Usage Report that is displayed in the System Troubleshooting () page for the number of counts, requests, and hits for each cache in Sterling B2B Integrator.
An increase in the number of requests and a decrease in the number of hits indicates that you have to increase the cache size for the affected cache. Each request that is not met with a hit requires a call to the database for data, which slows down the processing time and uses more resources, which could be used by other components of Sterling B2B Integrator.
For example, if the SchemaCache on the Cache Usage report has 5 counts, 5 requests, and 0 hits, it indicates that the schema cache may be too small for the number of requests from the cache or too small for the size of the documents used. Zero hits means that the business processes requesting the schema from the cache did not find the requested data and called the database to receive the schema data, which in turn slowed the processing time.