| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The listing cache prototype can be installed as a regular gateway. No extra config is required. Increasing java heap size is recommendedmandatory, and the disk storing /var/spool/caringo/cloudgateway should be SSD with preferably >=100Gb free capacity.
...
Monitor Cache Hit Rate
If you have telemetry and Grafana available, check the Listing Cache dashboard.
Check Response Time
Compare the response time before and after enabling the Listing Cache. Reduced response times, particularly for frequently requested data, indicate the cache functions correctly.
Resource Utilization
Monitor memory usage and CPU utilization. Increased memory usage and steady CPU activity are normal in a caching system, but excessively high CPU or memory usage may indicate misconfiguration or over-reliance on the cache.
Log Analysis
Review application logs for cache access events, if you have implemented custom logging for cache hits, misses, and evictions. This helps verify that requests are being served from the cache. This requires switching on DEBUG logging. Do we want customers to do that? If yes I can explain which log messages to look for.
Data Consistency Checks
Ensure that cached data remains consistent with the data source after cache invalidation events. You can periodically run checks comparing cache data with the database to verify consistency. The only way to do this is to setup a second gateway WITHOUT listing cache and compare listing results from both.