Question
1
Replies
156
Views
Incessant Technologies
Posted: June 15, 2018
Last activity: June 15, 2018
Closed
Rule Instance cache
Currently we are running on Pega cloud 7.2 version and we have below question.
We see many cache related Alerts(PEGA0016 & PEGA0017) in our Production instance, currently we have 15,000( rule instance limit size), To fix this issue we have done an exercise to find the ideal cache size(which is 30,000) based on our functionality. Now we have few questions on this.
1. If we increase cache size from 15000 to 30000, Does it impact on the JVM and heap memory ?(considering our prod infrastructure)
2. Once we do this change, Do we required to restart app server ?
3. Please recommend us if anything else need to be take care when we do this change.
Hi Santosh, for your questions:
1. If we increase cache size from 15000 to 30000, Does it impact on the JVM and heap memory ?(considering our prod infrastructure) ** Yes, the memory will grow a little bit which you can check on the Rule Cache Management page under estimated size.
2. Once we do this change, Do we required to restart app server ? ** Yes, a restart is needed.
Regarding the PEGA0016 and PEGA0017, you need to review those messages and understand which caches are being referred to here. You may need to make adjustments to one or more cache settings based on the messages being seen. The messages indicate that the limit has been exceeded and cache purging is occurring which can cause performance issues. Thus these messages should not be ignored. For more details, review the following:
https://community.pega.com/knowledgebase/articles/pega0016-alert-cache-reduced-target-size
https://community.pega.com/knowledgebase/articles/pega0017-alert-cache-exceeds-limit