JR47492: CMVC 229213 - The CalculationRegistry RangeCache memory footprint is large when there are many ranges for each scale.

7.0.0.9 for Developer Express
7.0.0.9 for Developer Professional
7.0.0.9 for Developer Enterprise
7.0.0-WS-WCServer-FP009
WebSphere Commerce Version 7.0.0.9 Fix Pack

APAR status

• Closed as program error.

Error description

• Each entry in the RangeCache represents a calculation scale and
  its ranges.  Each range is represented in memory by a
  CalculationRangeAccessBean object.  By keeping only the copy
  helper attributes in the RangeCache, the memory footprint can be
   reduced.
  

Local fix

Problem summary

• USERS AFFECTED:
   WebSphere Commerce users with many calculation scales with many
  calculation ranges.
  
   PROBLEM ABSTRACT:
   The CalculationRegistry RangeCache memory footprint is large
  when there are many ranges for each scale.
  
   BUSINESS IMPACT:
   Performance improvements can be achieved in some situations by
  reducing the footprint of each range in the RangeCache and
  increasing the number of ranges that can be cached.
  
   RECOMMENDATION:
  

Problem conclusion

• The interim fix for this APAR introduces a new configuration for
   the RangeCache, by introducing a new element in the
  InstanceProperties entry of the WebSphere Commerce configuration
   file.
  
   The default settings are:
   <com.ibm.commerce.order.calculation.RangeCache
  countRanges="false" maxSize="300" reduceMemory="true" />
  
   The countRanges and maxSize parameters can be used to control
  the memory footprint of the RangeCache in the
  CalculationRegistry. When countRanges is false (the default)
  then maxSize defaults to 300 and specifies the number of
  calculation scales that can be kept in the registry.  When
  countRanges is true, then maxSize defaults to 900 and specifies
  the number of scales plus the number of their ranges that can be
  kept in the registry.  These options are disabled by default.
  
   When reduceMemory is true (the default) then this iFix reduces
  the memory footprint of the RangeCache in the
  CalculationRegistry.  It can be set to false to revert to the
  previous behavior.
  
   To disable the reduceMemory feature or update either the
  countRanges or maxSize parameters,  add the
  "com.ibm.commerce.order.calculation.RangeCache" node as
  described inside the <InstanceProperties> node right before the
  closing tag </InstanceProperties> in the WebSphere Commerce
  configuration file. Then propagate the updated WebSphere
  Commerce configuration file to the EAR.
   -------------------------------------------------------------
   The latest available maintenance information can be obtained
  from the Recommended Fixes for WebSphere Commerce technote:
   http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP