Look at System Administrator->Perfomance Info->Caches.
Why would the Catalog hit ratio be low?
All the other ratios are nice and high.
What would it achieve if it was increased.
We have two massive catalogs and do not really have within them many items that would be accessed more frequently than others.
We sometimes get in appsvr db.log
CWPCM0018W:The query is delayed
I have looked at:
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
1 reply Latest Post - 2013-03-13T21:57:40Z by KaranBal
Pinned topic Performance Info Caches Catalog
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-13T21:57:40Z at 2013-03-13T21:57:40Z by KaranBal
KaranBal 270004GTF1108 PostsACCEPTED ANSWER
Re: Performance Info Caches Catalog2013-03-13T21:57:40Z in response to SystemAdminAbout cache hit ratio:
Low cache hit ratio means poor performance for the end users. Basically all computer programs use memory(RAM) to save frequently accessed data and they get the rest of the data from the database. Getting information from the database is very slow for obviously reasons and getting it through memory is fast. So if your cache hit ratio is low, then that means your system is fetching information from the database frequently causing slowness. That will also explain the slow queries. Better hit ratio can not prevent slow queries but they will lower the number.
Why is it low:
In the $TOP/etc/default, there are 2 files mdm-cache-config.properties and mdm-ehcache-config.xml which basically tell the system how many objects like items and specs to keep in memory. If you have a lot of memory but the application is configured to save few objects, then your hit ratio will be low. It is recommended to have atleast 90% hit ratio. To do so, increase the number of elements in these files.