My Oracle Support Banner

Catalog Repository Item Cache Tuning (Doc ID 1362861.1)

Last updated on NOVEMBER 23, 2019

Applies to:

Oracle Commerce Platform - Version 2006.3 and later
Information in this document applies to any platform.

Goal

Cache tuning is an important part of catalog design. A catalog that fits the business model well may not always be the most efficient format for storing information in memory. There are many factors that determine the design of the catalog:

1. Items for sale (skus, products)
2. Properties required for display (description, price, etc.)
3. Fields required for business rules (onSale etc.)
4. Import processes
5. Promotion mechanism
6. Bundling mechanism

If price lists are used, then these may have a close correlation with the product catalog. An implementation of price lists may result in several prices for every product or sku.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Purpose
 Is there anything I can do before starting the tuning exercise?
 How should I start sizing the cache?
 If I run out of memory or am concerned about running out of memory in the future, what should I do?
 I've identified large occupiers in the heap that are GSAItems. Now what do I do?
 I've trimmed down all I could. But my hit ratios are not affected!
 I see improvements. What do I do now?
 I've done all of the above. My hit ratios are over 85% but I run out of memory. What next?
 I've decreased a number of cache sizes. Now I have plenty of memory but I'm not getting the hit ratios I want. What next?
 Visual representation
 Caution!
 Conclusion
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.