General Page
Abstract:
Reference Data Caching is critical for performance and scalability. From experience, UI login time could jump to 30 seconds if the YFS_RESOURCE and YFS_RESOURCE_PERMISSION tables are not cached correctly. The application's overall throughput will drop significantly if caching is not enabled.
Body:
Important points to remember:
- Caching a entity reduces DB overhead, stretches JVM memory foot print. Enable caching for a DB table only after careful evaluation.
- Performance issues or network limits may surface with excessive RMI calls with frequent refresh of reference data cache.
- Monitor application logs for frequent cache refreshes, specifically look for YFS_INVENTORY_NODE_CONTROL, YPM_PRICE_LIST_LINE, YFS_ITEM, YFS_ITEM_SHIP_NODE, and either increase cache size (for relatively smaller tables that are reasonable to fit into memory), or disable the cache altogether (for very large table sizes) via customer overrides property file or via System Management console (SMA).
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PEW","label":"Sterling Order Management"},"ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
01 November 2021
UID
ibm16338517