MRU Report - Increasing cache size for specific Entry class
When we call admin api for mru report we get a response with the cache statistics. But when we see a problem for specific entry class that it is draining a lot we do not understand which DSS to create to increase the cache size. Do you have a help page or documentation explains this ? I gave some examples below.
You can also search for pega0016 and pega0017 and see the various instances of cache sizes that have been updated due to certain messages. You will want to review you PegaRULES-Alert log or PDC (if you are using it) which will tell you which cache the alert is being thrown from.
Thanks for quick reply. I already checked these articles. But I try to set DSS for specific entry class that I see the cache size is not good enough on MRU report. In this articles it only tell how to increase cache size for common types like PropertyReference. But in mru report with see lots of different type of cache settings. It would be very useful if a document shows us for each entry which DSS to create to increase or decrease the cache size. For example I could not find for some entry class how to create DSS to increase the limit. You can check my post I mentioned these settings below. The urls that you shared explain very high level and does not help me for this entry classes how to increase the size.
I see for the cache setting below it says in MRU report the limit is 6000. I just want to increase this to at least 40000. I did not understand the relation between PropertyReference and CachedInstanceSoftReference. If I increase property reference size CachedInstanceSoftReference limit still will be 6000. I am looking for that setting. For the others I think conclusion cache setting that you sent may work.
The article I sent and text I referenced seems to indicate that the soft references isn't controllable and that GC can occur to clean those up at any time: The softly referenced elements are not counted, like the mainstream cached elements, to determine the size of the cache as garbage collection may occur any time. If that needs to be explored further, I would suggest opening an SR.